Specification of Diagnostic Communication

Manager
AUTOSAR CP R20-11

Specification of Diagnostic
Document Title Communication Manager
Document Owner AUTOSAR
Document Responsibility AUTOSAR
Document Identification No 18

Document Status published

Part of AUTOSAR Standard Classic Platform
Part of Standard Release R20-11

Document Change History

Date Release Changed by Description
• Incorporation of Concept 671
Intrusion Detection System Manager
• Added DcmDspExternalSRDataEle-
AUTOSAR mentClass
2020-11-30 R20-11 Release • Updated the Error Classification
Management chapter
• minor corrections / clarifications /
editorial changes; For details please
refer to the ChangeDocumentation
• Incorporation of Concept NVData
Handling Enhancements
• Incorporation of PeriodicDID
Scheduler Type2
AUTOSAR • Renaming of the SRS_Diagnostics to
2019-11-28 R19-11 Release RS_Diagnostics
Management • minor corrections / clarifications /
editorial changes; For details please
refer to the ChangeDocumentation
• Changed Document Status from
Final to published

1 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• Incorporation of Concept 636

Security Extensions
• Rework of SenderReceiver interface
support for DIDs: Atomic
SenderReceiver interfaces added.
• Rework of SenderReceiver interface
support for controlling DIDs via
AUTOSAR service
2018-10-31 4.4.0 Release InputOutputControlByIdentifier
Management (0x2F)
• Support added for input signals for
the RequestRoutineResults (0x03)
subfunction of the RoutineControl
(0x31) service
• minor corrections / clarifications /
editorial changes; For details please
refer to the ChangeDocumentation
• Cleanup SRS_Diagnostic
requirement traceability
• Fix Dcm/Dem interactions
AUTOSAR inconsistencies
2017-12-08 4.3.1 Release • Add constraints requirements for
Management parameter configuration
• minor corrections / clarifications /
editorial changes; For details please
refer to the ChangeDocumentation
• Redesign interfaces between Dem
and Dcm
• Rework Security Access
AUTOSAR management
2016-11-30 4.3.0 Release • Add management for parallel support
Management for OBD and UDS protocols
• Clarify usage of Diagnosis scaling
• minor corrections / clarifications /
editorial changes; For details please
refer to the BWCStatement

2 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• Specify the NRCs to be sent by the

Dcm in case of Dem interfaces return
negative values.
AUTOSAR • Clarify Routine operation prototypes
2015-07-31 4.2.2 Release • Debugging support marked as
Management obsolete
• Minor corrections / clarifications /
editorial changes; For details please
refer to the Change Documentation
• Update to ISO 14229-1:2013 (Order
of NRCs, SID 0x19 and 0x28
extended subfunctions, SID 0x38)
AUTOSAR • Specify security mechanisms
2014-10-31 4.2.1 Release (security Lock time, static seed).
Management • Refine service
ReadDataByPeriodicIdentifier (0x2A)
and provide UUDT transfer.
• Reorganize the configuration
parameters for the routines.
• Added functional description for
AUTOSAR DIDRange usage
2014-03-31 4.1.3 Release • Added support for bootloader
Management interaction
• Revised the header file structure
• Editorial changes
• Created API tables for service
interfaces
• Provided synchronous and
asynchronous APIs for DataServices
AUTOSAR callouts
2013-10-31 4.1.2 Release • Harmonization for the length
Management parameter interpretation all over
RDBI, WDBI and RC services to be
in bytes
• Editorial changes
• Removed chapter(s) on change
documentation
• Added Response on Event support
AUTOSAR • Rework configuration for S/R
2013-03-15 4.1.1 communication
Administration
• Rework OBD Service $06
management

3 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• Change interaction with BswM

module for mode management
AUTOSAR • Change of callout configuration
2011-12-22 4.0.3 management for services and
Administration
sub-services processing
• Synchronous and asynchronous
clarification
• ComM_DCM_InactiveDiagnostic and
ComM_DCM_ActiveDiagnostic has
been defined as mandatory
interfaces.
•
DcmDslPeriodicTxConfirmationPduId
multiplicity changed and creation of
DcmDslPeriodicConnection
AUTOSAR parameter in order to link the
2009-12-18 4.0.1 confirmation Id with TxPdu Id for
Administration
PeriodicTransmission.
• Dem_GetDTCOfOBDFreezeFrame,
Dlt_ConditionCheckRead added as
optional interfaces
• DspInternal_<DiagnosticService>
Api moved to mandatory internal
interface to support the ECU
Supplier diagnosis.
• Rework of ReadData operation
• Add support of following UDS
services : ReadMemoryByAdress,
WriteMemoryByAdress,
RequestDownload, RequestUpload,
TransferData, RequestTransferExit,
CommunicationControl,
AUTOSAR ResponseOnEvent.
2009-12-04 3.1.4
Administration • Add of bootloader interaction
• Add of BswM interaction
• Add of IoHwAb interaction
• Add of DLT interaction
• Add of Signal based approach on
RTE interfaces
• Legal nvocation revised

4 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• Introduction of OBD support

• generation of artefacts from the
models according to the AUTOSAR
AUTOSAR process
2008-08-13 3.1.1 • Identification of requirements and
Administration
correct formulation of specification
items as requirements
• General cleanup
• Legal nvocation revised
• Rework of the interfaces with RTE
(remove of Central Diagnostic SWC
concept)
AUTOSAR • Correction of issues identified on
2007-12-21 3.0.1
Administration R2.1
• Document meta information
extended
• Small layout adaptations made
AUTOSAR • "Advice for users" revised
2007-01-24 2.1.15
Administration • "Revision Information" added
• Corrections in configuration chapter
• Rework on interface between DCM
AUTOSAR and DEM according to changes in
2.1.14 DEM SWS
Administration
• Corrections in Sequence diagram
• Addition of header files inclusions
• Legal disclaimer revised
AUTOSAR
2006-11-28 2.1 • Layout Adaptations
Administration
• Document structure adapted to
common Release 2.0 SWS Template

AUTOSAR • Major changes in chapter 10

2006-05-16 2.0
Administration
• Structure of document changed
partly
• Other changes see chapter 11
AUTOSAR
2005-05-31 1.0 • Initial release
Administration

5 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Disclaimer

This work (specification and/or software implementation) and the material contained in
it, as released by AUTOSAR, is for the purpose of information only. AUTOSAR and the
companies that have contributed to it shall not be liable for any use of the work.
The material contained in this work is protected by copyright and other types of intel-
lectual property rights. The commercial exploitation of the material contained in this
work requires a license to such intellectual property rights.
This work may be utilized or reproduced without any modification, in any form or by
any means, for informational purposes only. For any other purpose, no part of the work
may be utilized or reproduced, in any form or by any means, without permission in
writing from the publisher.
The work has been developed for automotive applications only. It has neither been
developed, nor tested for non-automotive applications.
The word AUTOSAR and the AUTOSAR logo are registered trademarks.

6 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Table of Contents
1 Introduction and functional overview 22

2 Acronyms and Abbreviations 24

2.1 Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 26
3 Related documentation 26
3.1 Input documents & related standards and norms . . . . . . . . . . . . 26
3.2 Related specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4 Constraints and assumptions 27
4.1 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.2 Applicability to car domains . . . . . . . . . . . . . . . . . . . . . . . . 29
4.3 Applicability to emission-related environments (OBD) . . . . . . . . . . 29
5 Dependencies to other modules 30

6 Requirements Tracing 31

7 Functional specification 46
7.1 Security Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
7.2 Error Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
7.2.1 Development Errors . . . . . . . . . . . . . . . . . . . . . . . 47
7.2.2 Runtime Errors . . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.2.3 Transient Faults . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.2.4 Production Errors . . . . . . . . . . . . . . . . . . . . . . . . 48
7.2.5 Extended Production Errors . . . . . . . . . . . . . . . . . . . 48
7.3 General design elements . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.3.1 Submodules within the Dcm module . . . . . . . . . . . . . . 49
7.3.2 Negative Response Code (NRC) . . . . . . . . . . . . . . . . 50
7.3.3 Non-volatile information . . . . . . . . . . . . . . . . . . . . . 50
7.3.4 Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7.3.4.1 Atomic types overview . . . . . . . . . . . . . . . . . 51
7.3.4.2 Data array types overview . . . . . . . . . . . . . . . 51
7.3.4.3 Data types constraints . . . . . . . . . . . . . . . . . 51
7.3.4.4 Dcm_OpStatusType . . . . . . . . . . . . . . . . . . 52
7.3.4.5 Dcm_Cemr_{DID}Type . . . . . . . . . . . . . . . . . 53
7.4 Diagnostic Session Layer (DSL) . . . . . . . . . . . . . . . . . . . . . . 53
7.4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.4.2 Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.4.3 Interaction with other modules . . . . . . . . . . . . . . . . . 53
7.4.4 Functional description . . . . . . . . . . . . . . . . . . . . . . 54
7.4.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . 54
7.4.4.2 Forward requests from the PduR module to the DSD
submodule . . . . . . . . . . . . . . . . . . . . . . . 55
7.4.4.2.1 Dcm_StartOfReception . . . . . . . . . . . . . 56

7 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.4.4.2.2 Dcm_CopyRxData . . . . . . . . . . . . . . . . 57
7.4.4.2.3 Dcm_TpRxIndication . . . . . . . . . . . . . . 57
7.4.4.3 Concurrent TesterPresent (”keep alive logic”) 58
7.4.4.3.1 Dcm_CopyTxData . . . . . . . . . . . . . . . . 58
7.4.4.3.2 Dcm_TpTxConfirmation . . . . . . . . . . . . . 59
7.4.4.4 Forward responses from the DSD submodule to the
PduR module . . . . . . . . . . . . . . . . . . . . . . 59
7.4.4.5 Generic Connection Handling . . . . . . . . . . . . . 60
7.4.4.6 Guarantee timing to tester by sending busy responses 61
7.4.4.7 Support of periodic transmission . . . . . . . . . . . 62
7.4.4.8 Support of ROE transmission . . . . . . . . . . . . . 62
7.4.4.8.1 ResponseOnEvent StateChar . . . . . . . . . 63
7.4.4.8.1.1 Initializing Dcm (1) . . . . . . . . . . . . 63
7.4.4.8.1.2 Transition from ’ROE cleared’ to ’ROE
stopped’ (2) . . . . . . . . . . . . . . . . 63
7.4.4.8.1.3 Transition from ’ROE stopped’ to ’ROE
cleared’ (3) . . . . . . . . . . . . . . . . 64
7.4.4.8.1.4 Transition from ’ROE stopped’ to ’ROE
started’ (4) . . . . . . . . . . . . . . . . 64
7.4.4.8.1.5 Transition from ’ROE started’ to ’ROE
stopped’ (5) . . . . . . . . . . . . . . . . 64
7.4.4.8.1.6 Transition from ’ROE started’ to ’ROE
started’ (6) . . . . . . . . . . . . . . . . 65
7.4.4.8.1.7 Transition from ’ROE started’ to ’ROE
cleared’ (7) . . . . . . . . . . . . . . . . 65
7.4.4.8.1.8 Transition from ’ROE cleared’ to ’ROE
cleared’ (8) . . . . . . . . . . . . . . . . 65
7.4.4.8.1.9 Transition from ’ROE cleared’ to ’ROE
started’ (9) . . . . . . . . . . . . . . . . 65
7.4.4.8.1.10 Transition from ’ROE stopped’ to ’ROE
stopped’ (10) . . . . . . . . . . . . . . . 66
7.4.4.8.2 ROE sub-functions . . . . . . . . . . . . . . . 66
7.4.4.8.3 EventWindowTime and StorageState . . . . . 66
7.4.4.8.4 Pre-configuration of ResponseOnEvent . . . . 68
7.4.4.8.5 Handling of event-trigger . . . . . . . . . . . . 69
7.4.4.8.5.1 ROE event-trigger onDTCSta-
tusChange (0x01) . . . . . . . . . . . . 69
7.4.4.8.5.2 ROE event-trigger onChangeOf-
DataIdentifier (0x03) . . . . . . . . . . . 70
7.4.4.8.6 Trigger a ServiceToRespondTo . . . . . . . . . 70
7.4.4.8.7 Send a ServiceToRespondTo . . . . . . . . . . 71
7.4.4.8.7.1 Roe transmission cycle . . . . . . . . . 72
7.4.4.8.8 ResponseOnEvent in multiple client environ-
ments . . . . . . . . . . . . . . . . . . . . . . . 72
7.4.4.9 Support of segmented response (paged-buffer) . . . 72

8 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.4.4.10 Support of ResponsePending response triggered by

the Application . . . . . . . . . . . . . . . . . . . . . 73
7.4.4.11 Manage security level . . . . . . . . . . . . . . . . . 73
7.4.4.11.1 Initialization sequence . . . . . . . . . . . . . . 74
7.4.4.11.2 AttemptCounter update . . . . . . . . . . . . . 75
7.4.4.12 Manage session state . . . . . . . . . . . . . . . . . 76
7.4.4.13 Manage authentication state . . . . . . . . . . . . . . 76
7.4.4.14 Keep track of active non-default sessions . . . . . . 78
7.4.4.15 Allow to modify timings . . . . . . . . . . . . . . . . . 79
7.4.4.16 Handling of different diagnostic protocols . . . . . . 80
7.4.4.16.1 Different service tables . . . . . . . . . . . . . 80
7.4.4.16.2 Prioritization of protocol . . . . . . . . . . . . . 80
7.4.4.16.3 Preemption of protocol . . . . . . . . . . . . . 81
7.4.4.16.4 Parallel OBD and UDS protocol processing . . 82
7.4.4.16.5 Detection of protocol start . . . . . . . . . . . . 83
7.4.4.16.6 Protocol stop . . . . . . . . . . . . . . . . . . . 84
7.4.4.17 Manage resources . . . . . . . . . . . . . . . . . . . 84
7.4.4.18 Communication Mode Handling . . . . . . . . . . . . 85
7.4.4.18.1 No Communication . . . . . . . . . . . . . . . 85
7.4.4.18.2 Silent Communication . . . . . . . . . . . . . . 86
7.4.4.18.3 Full Communication . . . . . . . . . . . . . . . 86
7.4.4.18.4 Diagnostic Activation State . . . . . . . . . . . 87
7.5 Diagnostic Service Dispatcher (DSD) . . . . . . . . . . . . . . . . . . . 88
7.5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
7.5.2 Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
7.5.2.1 Receive a request message and transmit a positive
response message . . . . . . . . . . . . . . . . . . . 89
7.5.2.2 Receive a request message and suppress a positive
response . . . . . . . . . . . . . . . . . . . . . . . . 89
7.5.2.3 Receive a request message and suppress a negative
response . . . . . . . . . . . . . . . . . . . . . . . . 89
7.5.2.4 Receive a request message and transmit a negative
response message . . . . . . . . . . . . . . . . . . . 89
7.5.2.5 Send a positive response message without corre-
sponding request . . . . . . . . . . . . . . . . . . . . 90
7.5.2.6 Segmented Responses (paged-buffer) . . . . . . . . 91
7.5.3 Interaction of the DSD with other modules . . . . . . . . . . . 91
7.5.3.1 Interaction of the DSD with the DSL main functionality 91
7.5.3.2 Interaction of the DSD with the DSP . . . . . . . . . . 91
7.5.4 Functional Description of the DSD . . . . . . . . . . . . . . . 92
7.5.4.1 Support checking the diagnostic service identifier
and adapting the diagnostic message . . . . . . . . 92
7.5.4.2 Handling of "suppressPosRspMsgIndicationBit" . . . 93
7.5.4.3 Verification functionality . . . . . . . . . . . . . . . . 94
7.5.4.3.1 Verification of the diagnostic service access
rights . . . . . . . . . . . . . . . . . . . . . . . 95

9 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.5.4.3.2 Verification of the Diagnostic Session . . . . . 96

7.5.4.3.3 Verification of the Service Security Access levels 97
7.5.4.3.4 Verification of the Service mode dependencies 98
7.5.4.4 Check format and subfunction support . . . . . . . . 98
7.5.4.4.1 Verification of the Manufacturer Application en-
vironment/permission . . . . . . . . . . . . . . 98
7.5.4.4.2 Verification of the Supplier Application environ-
ment/permission . . . . . . . . . . . . . . . . . 99
7.5.4.5 Distribution of diagnostic message to DSP submodule 100
7.5.4.6 Assemble positive or negative response . . . . . . . 100
7.5.4.6.1 Positive Response . . . . . . . . . . . . . . . . 100
7.5.4.6.2 Negative Response . . . . . . . . . . . . . . . 100
7.5.4.6.3 Suppression of response . . . . . . . . . . . . 101
7.5.4.7 Initiate transmission . . . . . . . . . . . . . . . . . . 101
7.6 Diagnostic Service Processing (DSP) . . . . . . . . . . . . . . . . . . . 102
7.6.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
7.6.1.1 Check format and subfunction support . . . . . . . . 103
7.6.1.2 Assemble response . . . . . . . . . . . . . . . . . . 103
7.6.1.3 Negative Response Codes handling . . . . . . . . . 103
7.6.1.4 Diagnostic mode declaration groups . . . . . . . . . 104
7.6.1.5 Environmental condition dependent execution . . . . 105
7.6.1.6 Sender/Receiver Communication . . . . . . . . . . . 108
7.6.1.7 Passing SwDataDefProps properties from DEXT file
to the Dcm Service SW-C . . . . . . . . . . . . . . . . 109
7.6.1.7.1 DcmDspDiagnosticDataElementRef
workflow . . . . . . . . . . . . . . . . . . . . . 109
7.6.1.7.2 DcmDspAlternativeDataType.DcmAp-
plicationDataType workflow . . . . . . . . 110
7.6.1.8 Asynchronous call behavior . . . . . . . . . . . . . . 110
7.6.2 UDS Services . . . . . . . . . . . . . . . . . . . . . . . . . . 111
7.6.2.1 General behavior using DEM interfaces . . . . . . . 112
7.6.2.2 Service 0x10 - Diagnostic Session Control . . . . . . 114
7.6.2.3 Service 0x11 - ECUReset . . . . . . . . . . . . . . . 114
7.6.2.4 Service 0x14 - Clear Diagnostic Information . . . . . 115
7.6.2.5 Service 0x19 - Read DTC Information . . . . . . . . . 117
7.6.2.5.1 Subfunctions 0x01, 0x07, 0x11 and 0x12 . . . 117
7.6.2.5.2 Subfunctions 0x02, 0x0A, 0x0F, 0x13, 0x15
and 0x17 . . . . . . . . . . . . . . . . . . . . . 118
7.6.2.5.3 Subfunction 0x08 . . . . . . . . . . . . . . . . 121
7.6.2.5.4 Subfunction 0x09 . . . . . . . . . . . . . . . . 122
7.6.2.5.5 Subfunctions 0x06/0x10/0x19 . . . . . . . . . 123
7.6.2.5.6 Subfunction 0x03 . . . . . . . . . . . . . . . . 125
7.6.2.5.7 Subfunctions 0x04 and 0x18 . . . . . . . . . . 127
7.6.2.5.8 Subfunction 0x05 . . . . . . . . . . . . . . . . 129
7.6.2.5.9 Subfunctions 0x0B, 0x0C, 0x0D and 0x0E . . 130
7.6.2.5.10 Subfunction 0x14 . . . . . . . . . . . . . . . . 131

10 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.6.2.5.11 Subfunction 0x42 . . . . . . . . . . . . . . . . 132

7.6.2.5.12 Subfunction 0x55 . . . . . . . . . . . . . . . . 134
7.6.2.6 Service 0x22 - ReadDataByIdentifier . . . . . . . . . 135
7.6.2.6.1 UDS DID . . . . . . . . . . . . . . . . . . . . . 138
7.6.2.6.2 OBD DID . . . . . . . . . . . . . . . . . . . . . 140
7.6.2.7 Service 0x24 - ReadScalingDataByIdentifier . . . . . 141
7.6.2.8 Service 0x27 - SecurityAccess . . . . . . . . . . . . 142
7.6.2.9 Service 0x28 - CommunicationControl . . . . . . . . 144
7.6.2.10 Service 0x29 - Authentication . . . . . . . . . . . . . 147
7.6.2.10.1 De-authentication . . . . . . . . . . . . . . . . 149
7.6.2.10.2 Verify Certificates . . . . . . . . . . . . . . . . 149
7.6.2.10.3 Proof of ownership client . . . . . . . . . . . . 154
7.6.2.10.4 Definition and verification of roles . . . . . . . 156
7.6.2.10.5 Definition and verification of white lists . . . . . 157
7.6.2.10.6 AuthenticationConfiguration . . . . . . . . . . 160
7.6.2.11 Service 0x2A - ReadDataByPeriodicIdentifier . . . . 160
7.6.2.11.1 Scheduler PeriodicTransmission . . . . . . . . 163
7.6.2.12 Service 0x2C - DynamicallyDefineDataIdentifier . . . 172
7.6.2.13 Service 0x2E - WriteDataByIdentifier . . . . . . . . . 174
7.6.2.14 Service 0x2F - InputOutputControlByIdentifier . . . . 177
7.6.2.15 Service 0x31 - RoutineControl . . . . . . . . . . . . . 188
7.6.2.16 Service 0x3E - Tester Present . . . . . . . . . . . . . 196
7.6.2.17 Service 0x3D - WriteMemoryByAddress . . . . . . . 196
7.6.2.18 Service 0x23 - ReadMemoryByAddress . . . . . . . 198
7.6.2.19 Service 0x34 - RequestDownload . . . . . . . . . . . 199
7.6.2.20 Service 0x35 - RequestUpload . . . . . . . . . . . . 200
7.6.2.21 Service 0x36 - TransferData . . . . . . . . . . . . . . 201
7.6.2.22 Service 0x37 - RequestTransferExit . . . . . . . . . . 203
7.6.2.23 Service 0x38 - RequestFileTransfer . . . . . . . . . . 203
7.6.2.24 Service 0x85 - ControlDTCSetting . . . . . . . . . . 205
7.6.2.25 Service 0x87 - LinkControl . . . . . . . . . . . . . . . 206
7.6.3 OBD Services . . . . . . . . . . . . . . . . . . . . . . . . . . 206
7.6.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . 206
7.6.3.2 General behavior . . . . . . . . . . . . . . . . . . . . 207
7.6.3.3 Service $01 - Request Current Powertrain Diagnos-
tic Data . . . . . . . . . . . . . . . . . . . . . . . . . 208
7.6.3.4 Service $02 - Request Power Train FreezeFrame Data 210
7.6.3.4.1 Service $02 - PID$02 . . . . . . . . . . . . . . 211
7.6.3.4.2 Service $02 - availability PID . . . . . . . . . . 211
7.6.3.4.3 Service $02 - other PIDs . . . . . . . . . . . . 211
7.6.3.5 Service $03 $07 $0A - Obtaining DTCs . . . . . . . 212
7.6.3.6 Service $04 - Clear/reset emission-related diagnos-
tic information . . . . . . . . . . . . . . . . . . . . . . 214
7.6.3.7 Service $06 - Request On-Board Monitoring Test-
results for Specific Monitored Systems . . . . . . . . 215
7.6.3.7.1 General requirements . . . . . . . . . . . . . . 215

11 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.6.3.7.2 Test results obtained via Dem interaction . . . 215

7.6.3.8 Service $08 - Request Control of On-Board System,
Test or Component . . . . . . . . . . . . . . . . . . . 216
7.6.3.9 Service $09 - Request Vehicle Information . . . . . . 217
7.6.4 Interaction usecases . . . . . . . . . . . . . . . . . . . . . . . 218
7.6.4.1 Jump to Bootloader . . . . . . . . . . . . . . . . . . . 218
7.6.4.2 Jump due to ECUReset . . . . . . . . . . . . . . . . 221
7.6.4.3 Jump from Bootloader / ECUReset . . . . . . . . . . 221
7.6.4.4 Flags management . . . . . . . . . . . . . . . . . . . 222
7.6.4.4.1 Jump to Bootloader . . . . . . . . . . . . . . . 222
7.6.4.4.2 Jump from Bootloader . . . . . . . . . . . . . . 222
7.7 Error notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
7.8 Synchronous and Asynchronous implementation . . . . . . . . . . . . 223
7.9 DID configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
7.9.1 Individual DID . . . . . . . . . . . . . . . . . . . . . . . . . . 224
7.9.2 DID ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
7.10 Startup behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
8 API specification 227
8.1 Imported types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
8.2 Type definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
8.2.1 Dcm_StatusType . . . . . . . . . . . . . . . . . . . . . . . . . 228
8.2.2 Dcm_CommunicationModeType . . . . . . . . . . . . . . . . 229
8.2.3 Dcm_ConfigType . . . . . . . . . . . . . . . . . . . . . . . . . 230
8.2.4 Dcm_ReturnReadMemoryType . . . . . . . . . . . . . . . . . 230
8.2.5 Dcm_ReturnWriteMemoryType . . . . . . . . . . . . . . . . . 230
8.2.6 Dcm_EcuStartModeType . . . . . . . . . . . . . . . . . . . . 231
8.2.7 Dcm_ProgConditionsType . . . . . . . . . . . . . . . . . . . 231
8.2.8 Dcm_MsgItemType . . . . . . . . . . . . . . . . . . . . . . . 232
8.2.9 Dcm_MsgType . . . . . . . . . . . . . . . . . . . . . . . . . . 232
8.2.10 Dcm_MsgLenType . . . . . . . . . . . . . . . . . . . . . . . . 233
8.2.11 Dcm_MsgAddInfoType . . . . . . . . . . . . . . . . . . . . . 233
8.2.12 Dcm_IdContextType . . . . . . . . . . . . . . . . . . . . . . . 234
8.2.13 Dcm_MsgContextType . . . . . . . . . . . . . . . . . . . . . 234
8.2.14 Dcm_ExtendedOpStatusType . . . . . . . . . . . . . . . . . 235
8.3 Function definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
8.3.1 Functions provided for other BSW components . . . . . . . . 236
8.3.1.1 Dcm_Init . . . . . . . . . . . . . . . . . . . . . . . . . 236
8.3.1.2 Dcm_GetVersionInfo . . . . . . . . . . . . . . . . . . 237
8.3.1.3 Dcm_DemTriggerOnDTCStatus . . . . . . . . . . . . 237
8.3.1.4 Dcm_GetVin . . . . . . . . . . . . . . . . . . . . . . 238
8.3.1.5 Dcm_BndMWriteBlockFinish . . . . . . . . . . . . . 238
8.3.2 Functions provided to BSW modules and to SW-Cs . . . . . 239
8.3.2.1 Dcm_SetDeauthenticatedRole . . . . . . . . . . . . 239
8.3.2.2 Dcm_GetSecurityLevel . . . . . . . . . . . . . . . . . 239
8.3.2.3 Dcm_GetSesCtrlType . . . . . . . . . . . . . . . . . 240

12 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.3.2.4 Dcm_GetActiveProtocol . . . . . . . . . . . . . . . . 240

8.3.2.5 Dcm_ResetToDefaultSession . . . . . . . . . . . . . 241
8.3.2.6 Dcm_TriggerOnEvent . . . . . . . . . . . . . . . . . 241
8.3.2.7 Dcm_ SetActiveDiagnostic . . . . . . . . . . . . . . . 242
8.4 Callback notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
8.4.1 Dcm_StartOfReception . . . . . . . . . . . . . . . . . . . . . 243
8.4.2 Dcm_CopyRxData . . . . . . . . . . . . . . . . . . . . . . . . 244
8.4.3 Dcm_TpRxIndication . . . . . . . . . . . . . . . . . . . . . . 245
8.4.4 Dcm_CopyTxData . . . . . . . . . . . . . . . . . . . . . . . . 245
8.4.5 Dcm_TpTxConfirmation . . . . . . . . . . . . . . . . . . . . . 247
8.4.6 Dcm_TxConfirmation . . . . . . . . . . . . . . . . . . . . . . 247
8.4.7 Dcm_ComM_NoComModeEntered . . . . . . . . . . . . . . 248
8.4.8 Dcm_ComM_SilentComModeEntered . . . . . . . . . . . . . 248
8.4.9 Dcm_ComM_FullComModeEntered . . . . . . . . . . . . . . 248
8.4.10 Dcm_CsmAsyncJobFinished . . . . . . . . . . . . . . . . . . 249
8.4.11 Dcm_KeyMAsyncCertificateVerifyFinished . . . . . . . . . . 249
8.5 Callout Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
8.5.1 Dcm_ReadMemory . . . . . . . . . . . . . . . . . . . . . . . 250
8.5.2 Dcm_WriteMemory . . . . . . . . . . . . . . . . . . . . . . . 251
8.5.3 Dcm_SetProgConditions . . . . . . . . . . . . . . . . . . . . 252
8.5.4 Dcm_GetProgConditions . . . . . . . . . . . . . . . . . . . . 253
8.5.5 Dcm_ProcessRequestAddFile . . . . . . . . . . . . . . . . . 254
8.5.6 Dcm_ProcessRequestDeleteFile . . . . . . . . . . . . . . . . 255
8.5.7 Dcm_ProcessRequestReplaceFile . . . . . . . . . . . . . . . 256
8.5.8 Dcm_ProcessRequestReadFile . . . . . . . . . . . . . . . . 257
8.5.9 Dcm_ProcessRequestReadDir . . . . . . . . . . . . . . . . . 258
8.5.10 Dcm_WriteFile . . . . . . . . . . . . . . . . . . . . . . . . . . 259
8.5.11 Dcm_ReadFileOrDir . . . . . . . . . . . . . . . . . . . . . . . 260
8.6 Scheduled functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
8.6.1 Dcm_MainFunction . . . . . . . . . . . . . . . . . . . . . . . 260
8.7 Expected interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
8.7.1 Mandatory interfaces . . . . . . . . . . . . . . . . . . . . . . 261
8.7.2 Optional interfaces . . . . . . . . . . . . . . . . . . . . . . . . 261
8.7.3 Configurable interfaces . . . . . . . . . . . . . . . . . . . . . 265
8.7.3.1 SecurityAccess . . . . . . . . . . . . . . . . . . . . . 265
8.7.3.1.1 GetSeed . . . . . . . . . . . . . . . . . . . . . 265
8.7.3.1.2 CompareKey . . . . . . . . . . . . . . . . . . . 266
8.7.3.1.3 GetSecurityAttemptCounter . . . . . . . . . . 267
8.7.3.1.4 SetSecurityAttemptCounter . . . . . . . . . . . 268
8.7.3.2 DataServices . . . . . . . . . . . . . . . . . . . . . . 268
8.7.3.2.1 ReadData . . . . . . . . . . . . . . . . . . . . 268
8.7.3.2.2 WriteData . . . . . . . . . . . . . . . . . . . . 270
8.7.3.2.3 ReadDataLength . . . . . . . . . . . . . . . . . 273
8.7.3.2.4 ConditionCheckRead . . . . . . . . . . . . . . 274
8.7.3.2.5 GetScalingInformation . . . . . . . . . . . . . 275
8.7.3.2.6 ReturnControlToECU . . . . . . . . . . . . . . 276

13 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.7.3.2.7 ResetToDefault . . . . . . . . . . . . . . . . . 277

8.7.3.2.7.1 Synchronous interface . . . . . . . . . . 277
8.7.3.2.7.2 Asynchronous interface . . . . . . . . . 278
8.7.3.2.8 FreezeCurrentState . . . . . . . . . . . . . . . 279
8.7.3.2.8.1 Synchronous interface . . . . . . . . . . 279
8.7.3.2.8.2 Asynchronous interface . . . . . . . . . 280
8.7.3.2.9 ShortTermAdjustment . . . . . . . . . . . . . . 281
8.7.3.2.9.1 Synchronous interface . . . . . . . . . . 281
8.7.3.2.9.2 Asynchronous interface . . . . . . . . . 282
8.7.3.3 DataServices_DIDRange . . . . . . . . . . . . . . . 284
8.7.3.3.1 IsDidAvailable . . . . . . . . . . . . . . . . . . 284
8.7.3.3.2 ReadDidData . . . . . . . . . . . . . . . . . . . 284
8.7.3.3.3 WriteDidData . . . . . . . . . . . . . . . . . . . 285
8.7.3.3.4 ReadDidRangeDataLength . . . . . . . . . . . 286
8.7.3.4 InfoTypesServices . . . . . . . . . . . . . . . . . . . 287
8.7.3.4.1 GetInfotypeValueData . . . . . . . . . . . . . . 287
8.7.3.5 RoutineServices . . . . . . . . . . . . . . . . . . . . 287
8.7.3.5.1 Xxx_Start Operation . . . . . . . . . . . . . . . 287
8.7.3.5.2 Xxx_StartConfirmation Operation . . . . . . . 288
8.7.3.5.3 Xxx_Stop Operation . . . . . . . . . . . . . . . 289
8.7.3.5.4 Xxx_StopConfirmation Operation . . . . . . . 290
8.7.3.5.5 Xxx_RequestResults Operation . . . . . . . . 290
8.7.3.5.6 Xxx_RequestResultsConfirmation Operation . 291
8.7.3.6 RequestControlServices . . . . . . . . . . . . . . . . 292
8.7.3.6.1 RequestControl callout . . . . . . . . . . . . . 292
8.7.3.7 CallbackDCMRequestServices . . . . . . . . . . . . 293
8.7.3.7.1 StartProtocol . . . . . . . . . . . . . . . . . . . 293
8.7.3.7.2 StopProtocol . . . . . . . . . . . . . . . . . . . 293
8.7.3.8 ServiceRequestNotification . . . . . . . . . . . . . . 294
8.7.3.8.1 Indication . . . . . . . . . . . . . . . . . . . . . 294
8.7.3.8.2 Confirmation . . . . . . . . . . . . . . . . . . . 295
8.7.3.9 ClearDTCCheckFnc . . . . . . . . . . . . . . . . . . 296
8.7.3.10 UploadDownloadServices . . . . . . . . . . . . . . . 296
8.7.3.10.1 ProcessRequestDownload . . . . . . . . . . . 296
8.7.3.10.2 ProcessRequestTransferExit . . . . . . . . . . 297
8.7.3.10.3 ProcessRequestUpload . . . . . . . . . . . . . 298
8.7.3.10.4 ProcessTransferDataRead . . . . . . . . . . . 299
8.7.3.10.5 ProcessTransferDataWrite . . . . . . . . . . . 300
8.8 Dcm as Service-Component . . . . . . . . . . . . . . . . . . . . . . . . 301
8.8.1 Implementation Data Types . . . . . . . . . . . . . . . . . . . 301
8.8.1.1 Dcm_OpStatusType . . . . . . . . . . . . . . . . . . 301
8.8.1.2 Dcm_ConfirmationStatusType . . . . . . . . . . . . . 301
8.8.1.3 Dcm_SecLevelType . . . . . . . . . . . . . . . . . . 302
8.8.1.4 Dcm_SesCtrlType . . . . . . . . . . . . . . . . . . . 302
8.8.1.5 Dcm_ProtocolType . . . . . . . . . . . . . . . . . . . 303
8.8.1.6 Dcm_NegativeResponseCodeType . . . . . . . . . . 304

14 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.1.7 Dcm_DataElementType_{Data}Type . . . . . . . . . 307

8.8.1.8 Dcm_DataElementType_{Data}ArrayType . . . . . . 308
8.8.1.9 Dcm_DataElementType_{Data}PrimitiveType . . . . 309
8.8.1.10 Dcm_DataArrayTypeUint8_{Data}Type . . . . . . . . 310
8.8.1.11 {DID}_Struct_DataType . . . . . . . . . . . . . . . . 311
8.8.1.12 Dcm_RangeArray_{Range}Type . . . . . . . . . . . 311
8.8.1.13 Dcm_InfoTypeServicesArray_{VehInfoData}Type . . 312
8.8.1.14 Dcm_RequestControlServicesInArray_{Tid}Type . . 312
8.8.1.15 Dcm_RequestControlServicesOutArray_{Tid}Type . 312
8.8.1.16 Dcm_ScalingInfoArray_{Data}Type . . . . . . . . . . 313
8.8.1.17 Dcm_RequestDataOut_{Routine}_{Signal}PrimitivType313
8.8.1.18 Dcm_RequestDataIn_{Routine}_{Signal}PrimitiveType 314
8.8.1.19 Dcm_RequestDataOut_{Routine}_{Signal}Type . . . 315
8.8.1.20 Dcm_RequestDataIn_{Routine}_{Signal}Type . . . . 315
8.8.1.21 Dcm_RequestDataOut_{Routine}_{Signal}ArrayType 316
8.8.1.22 Dcm_RequestDataIn_{Routine}_{Signal}ArrayType . 317
8.8.1.23 Dcm_RequestFlexibleOutArrayData_{Routine}_
{Signal}Type . . . . . . . . . . . . . . . . . . . . . . . 318
8.8.1.24 Dcm_RequestFlexibleInArrayData_{Routine}_{Sig-
nal}Type . . . . . . . . . . . . . . . . . . . . . . . . . 318
8.8.1.25 Dcm_StartDataIn_{Routine}_{Signal}PrimitivType . . 319
8.8.1.26 Dcm_StartDataIn_{Routine}_{Signal}Type . . . . . . 319
8.8.1.27 Dcm_StartDataIn_{Routine}_{Signal}ArrayType . . . 320
8.8.1.28 Dcm_StartDataOut_{Routine}_{Signal}PrimitivType . 321
8.8.1.29 Dcm_StartDataOut_{Routine}_{Signal}Type . . . . . 321
8.8.1.30 Dcm_StartDataOut_{Routine}_{Signal}ArrayType . . 322
8.8.1.31 Dcm_StartFlexibleInArrayData_{Routine}_{Sig-
nal}Type . . . . . . . . . . . . . . . . . . . . . . . . . 323
8.8.1.32 Dcm_StartFlexibleOutArrayData_{Routine}_{Sig-
nal}Type . . . . . . . . . . . . . . . . . . . . . . . . . 323
8.8.1.33 Dcm_StopDataIn_{Routine}_{Signal}PrimitivType . . 324
8.8.1.34 Dcm_StopDataIn_{Routine}_{Signal}Type . . . . . . 325
8.8.1.35 Dcm_StopDataIn_{Routine}_{Signal}ArrayType . . . 325
8.8.1.36 Dcm_StopDataOut_{Routine}_{Signal}PrimitivType . 326
8.8.1.37 Dcm_StopDataOut_{Routine}_{Signal}Type . . . . . 327
8.8.1.38 Dcm_StopDataOut_{Routine}_{Signal}ArrayType . . 327
8.8.1.39 Dcm_StopFlexibleInArrayData_{Routine}_{Sig-
nal}Type . . . . . . . . . . . . . . . . . . . . . . . . . 328
8.8.1.40 Dcm_StopFlexibleOutArrayData_{Routine}_{Sig-
nal}Type . . . . . . . . . . . . . . . . . . . . . . . . . 329
8.8.1.41 Dcm_KeyArray_{SecurityLevel}Type . . . . . . . . . 329
8.8.1.42 Dcm_SeedArray_{SecurityLevel}Type . . . . . . . . 329
8.8.1.43 Dcm_SecurityAccessDataRecordArray_{Secu-
rityLevel}Type . . . . . . . . . . . . . . . . . . . . . . 330
8.8.1.44 Dcm_RequestDataArrayType . . . . . . . . . . . . . 330
8.8.1.45 Dcm_ControlMask_{DID}Type . . . . . . . . . . . . . 330

15 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.1.46 Dcm_inputOutputControlParameterType . . . . . . . 331

8.8.1.47 Dcm_IOOperationRequest_{DID}Type . . . . . . . . 332
8.8.1.48 Dcm_IOOperationResponseType . . . . . . . . . . . 332
8.8.1.49 Dcm_DidSupportedType . . . . . . . . . . . . . . . . 333
8.8.1.50 Dcm_FileAndDirNameType . . . . . . . . . . . . . . 333
8.8.1.51 Dcm_ResponseDataArrayType . . . . . . . . . . . . 334
8.8.1.52 Dcm_AuthenticationRoleType . . . . . . . . . . . . . 334
8.8.1.53 Dcm_ControlMask_{Data}ArrayType . . . . . . . . . 334
8.8.1.54 Dcm_Cemr_{DID}Type . . . . . . . . . . . . . . . . . 335
8.8.2 Sender-Receiver-Interfaces . . . . . . . . . . . . . . . . . . . 335
8.8.2.1 DataServices_{DID} . . . . . . . . . . . . . . . . . . 335
8.8.2.2 DataServices_{Data} . . . . . . . . . . . . . . . . . . 336
8.8.2.3 IOControlRequest_{DID} . . . . . . . . . . . . . . . . 336
8.8.2.4 IOControlResponse_{DID} . . . . . . . . . . . . . . . 337
8.8.3 Client-Server-Interfaces . . . . . . . . . . . . . . . . . . . . . 338
8.8.3.1 SecurityAccess_{SecurityLevel} . . . . . . . . . . . . 338
8.8.3.2 DataServices_{Data} . . . . . . . . . . . . . . . . . . 341
8.8.3.2.1 ReadData . . . . . . . . . . . . . . . . . . . . 357
8.8.3.2.2 WriteData . . . . . . . . . . . . . . . . . . . . 357
8.8.3.2.3 ReadDataLength . . . . . . . . . . . . . . . . . 357
8.8.3.2.4 ConditionCheckRead . . . . . . . . . . . . . . 358
8.8.3.2.5 GetScalingInformation . . . . . . . . . . . . . 358
8.8.3.2.6 ReturnControlToEcu . . . . . . . . . . . . . . . 358
8.8.3.2.7 ResetToDefault . . . . . . . . . . . . . . . . . 358
8.8.3.2.8 FreezeCurrentState . . . . . . . . . . . . . . . 358
8.8.3.2.9 ShortTermAdjustment . . . . . . . . . . . . . . 358
8.8.3.3 DataServices_DIDRange_{Range} . . . . . . . . . . 358
8.8.3.4 InfotypeServices_{VehInfoData} . . . . . . . . . . . . 361
8.8.3.5 RoutineServices_{RoutineName} . . . . . . . . . . . 362
8.8.3.6 RequestControlServices_{Tid} . . . . . . . . . . . . 377
8.8.3.7 CallbackDCMRequestServices . . . . . . . . . . . . 378
8.8.3.8 ServiceRequestNotification . . . . . . . . . . . . . . 379
8.8.3.9 UploadDownloadServices . . . . . . . . . . . . . . . 381
8.8.3.10 RequestFileTransfer . . . . . . . . . . . . . . . . . . 387
8.8.3.11 DCMServices . . . . . . . . . . . . . . . . . . . . . . 395
8.8.3.12 DCM_Roe . . . . . . . . . . . . . . . . . . . . . . . . 397
8.8.3.13 Authentication . . . . . . . . . . . . . . . . . . . . . . 397
8.8.4 NvDataInterface . . . . . . . . . . . . . . . . . . . . . . . . . 398
8.8.4.1 DataServices_{DID} . . . . . . . . . . . . . . . . . . 398
8.8.5 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
8.8.5.1 Dcm_CallbackDCMRequestServices_{Name} . . . . 400
8.8.5.2 DataServices_DIDRange_{Range} . . . . . . . . . . 400
8.8.5.3 DataServices_{DID} . . . . . . . . . . . . . . . . . . 400
8.8.5.4 DataServices_{Data} . . . . . . . . . . . . . . . . . . 401
8.8.5.5 IOControlRequest_{DID} . . . . . . . . . . . . . . . . 402
8.8.5.6 IOControlResponse_{DID} . . . . . . . . . . . . . . . 403

16 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.5.7 DCM_Roe_{RoeName} . . . . . . . . . . . . . . . . 403

8.8.5.8 DCMServices . . . . . . . . . . . . . . . . . . . . . . 403
8.8.5.9 InfotypeServices_{VehInfoData} . . . . . . . . . . . . 404
8.8.5.10 RequestControlServices_{Tid} . . . . . . . . . . . . 404
8.8.5.11 RequestFileTransfer . . . . . . . . . . . . . . . . . . 404
8.8.5.12 ServiceRequestManufacturerNotification_{Name} . . 405
8.8.5.13 ServiceRequestSupplierNotification_{Name} . . . . . 405
8.8.5.14 RoutineServices_{RoutineName} . . . . . . . . . . . 405
8.8.5.15 SecurityAccess_{SecurityLevel} . . . . . . . . . . . . 406
8.8.5.16 Dcm_DiagnosticSessionControlModeSwitchInterface 406
8.8.5.17 Dcm_EcuResetModeSwitchInterface . . . . . . . . . 406
8.8.5.18 Dcm_ModeRapidPowerShutDownModeSwitchInter-
face . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
8.8.5.19 Dcm_CommunicationControlModeSwitchInterface_
{ComMChannelName} . . . . . . . . . . . . . . . . . 407
8.8.5.20 Dcm_ControlDTCSettingModeSwitchInterface . . . . 407
8.8.5.21 Dcm_ResponseOnEventModeSwitchInterface_
{RoeEventID} . . . . . . . . . . . . . . . . . . . . . . 407
8.8.5.22 Dcm_SecurityAccessModeSwitchInterface . . . . . . 408
8.8.5.23 Dcm_UploadDownloadServices . . . . . . . . . . . . 408
8.8.5.24 Dcm_Authentication_{Connection} . . . . . . . . . . 408
8.8.6 ModeDeclarationGroups . . . . . . . . . . . . . . . . . . . . 409
8.8.6.1 DcmDiagnosticSessionControl . . . . . . . . . . . . 409
8.8.6.2 DcmEcuReset . . . . . . . . . . . . . . . . . . . . . 409
8.8.6.3 DcmModeRapidPowerShutDown . . . . . . . . . . . 410
8.8.6.4 DcmCommunicationControl . . . . . . . . . . . . . . 410
8.8.6.5 DcmControlDTCSetting . . . . . . . . . . . . . . . . 411
8.8.6.6 DcmResponseOnEvent . . . . . . . . . . . . . . . . 411
8.8.6.7 DcmSecurityAccess . . . . . . . . . . . . . . . . . . 412
8.8.6.8 DcmAuthenticationState . . . . . . . . . . . . . . . . 412
8.8.7 Mode-Switch-Interfaces . . . . . . . . . . . . . . . . . . . . . 413
8.8.7.1 Dcm_DiagnosticSessionControlModeSwitchInterface 413
8.8.7.2 Dcm_EcuResetModeSwitchInterface . . . . . . . . . 413
8.8.7.3 Dcm_ModeRapidPowerShutDownModeSwitchInter-
face . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
8.8.7.4 Dcm_CommunicationControlModeSwitchInterface . 413
8.8.7.5 Dcm_ControlDTCSettingModeSwitchInterface . . . . 414
8.8.7.6 Dcm_ResponseOnEventModeSwitchInterface . . . . 414
8.8.7.7 Dcm_SecurityAccessModeSwitchInterface . . . . . . 414
8.8.7.8 Dcm_AuthenticationStateModeSwitchInterface . . . 415
8.9 External diagnostic service processing . . . . . . . . . . . . . . . . . . 415
8.9.1 <Module>_<DiagnosticService> . . . . . . . . . . . . . . . . 415
8.9.2 <Module>_<DiagnosticService>_<SubService> . . . . . . . 416
8.10 Internal interfaces (not normative) . . . . . . . . . . . . . . . . . . . . . 417
8.10.1 DslInternal_SetSecurityLevel . . . . . . . . . . . . . . . . . . 417
8.10.2 DslInternal_SetSesCtrlType . . . . . . . . . . . . . . . . . . . 417

17 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.10.3 DspInternal_DcmConfirmation . . . . . . . . . . . . . . . . . 417

8.10.4 DslInternal_ResponseOnOneEvent . . . . . . . . . . . . . . 417
8.10.5 DslInternal_ResponseOnOneDataByPeriodicId . . . . . . . . 418
8.10.6 DsdInternal_StartPagedProcessing . . . . . . . . . . . . . . 418
8.10.7 DspInternal_CancelPagedBufferProcessing . . . . . . . . . . 418
8.10.8 DsdInternal_ProcessPage . . . . . . . . . . . . . . . . . . . 418
9 Sequence diagrams 418
9.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
9.2 DSL (Diagnostic Session Layer) . . . . . . . . . . . . . . . . . . . . . . 419
9.2.1 Start Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . 419
9.2.2 Process Busy behavior . . . . . . . . . . . . . . . . . . . . . 420
9.2.3 Update Diagnostic Session Control when timeout occurs . . 421
9.2.4 Process single response of ReadDataByPeriodicIdentifier . . 422
9.2.5 Process single event-triggered response of ResponseOnEvent423
9.2.6 Process concurrent requests . . . . . . . . . . . . . . . . . . 424
9.2.7 Interface to ComManager . . . . . . . . . . . . . . . . . . . . 425
9.2.7.1 Handling in Default Session . . . . . . . . . . . . . . 425
9.2.7.2 Handling in Non-Default Session . . . . . . . . . . . 426
9.2.7.3 Session transitions . . . . . . . . . . . . . . . . . . . 426
9.2.7.4 Communication States . . . . . . . . . . . . . . . . . 427
9.2.8 Receive request message and transmit negative response
message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
9.2.9 Process Service Request with paged-buffer . . . . . . . . . . 430
9.2.10 Process copy data in reception . . . . . . . . . . . . . . . . . 432
9.2.11 Process copy data in transmission . . . . . . . . . . . . . . . 433
9.3 DSP (Diagnostic Service Processing) . . . . . . . . . . . . . . . . . . . 433
9.3.1 Interface DSP - DEM (service 0x19, 0x14, 0x85) . . . . . . . 433
9.3.2 Interface special services . . . . . . . . . . . . . . . . . . . . 433
9.3.2.1 Process Diagnostic Session Control . . . . . . . . . 433
9.3.2.2 Process Tester Present . . . . . . . . . . . . . . . . 434
9.3.2.3 Process Security Access . . . . . . . . . . . . . . . . 435
9.3.2.4 Process ResponseOnEvent OnDtcChange . . . . . 436
9.3.2.5 Process ResponseOnEvent OnChangeOfDataIden-
tifier . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
9.3.2.6 Process Jump to Bootloader . . . . . . . . . . . . . . 438
10 Configuration specification 438
10.1 How to read this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . 439
10.2 Containers and configuration parameters . . . . . . . . . . . . . . . . . 439
10.2.1 Dcm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
10.2.2 DcmConfigSet . . . . . . . . . . . . . . . . . . . . . . . . . . 441
10.2.2.1 DcmPageBufferCfg . . . . . . . . . . . . . . . . . . . 441
10.2.2.2 DcmProcessingConditions . . . . . . . . . . . . . . . 442
10.2.3 DcmDsd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
10.2.3.1 DcmDsd . . . . . . . . . . . . . . . . . . . . . . . . . 445
10.2.3.2 DcmDsdService . . . . . . . . . . . . . . . . . . . . 447

18 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

10.2.3.3 DcmDsdServiceRequestManufacturerNotification . . 451

10.2.3.4 DcmDsdServiceRequestSupplierNotification . . . . . 452
10.2.3.5 DcmDsdServiceTable . . . . . . . . . . . . . . . . . 452
10.2.3.6 DcmDsdSubService . . . . . . . . . . . . . . . . . . 453
10.2.4 DcmDsl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
10.2.4.1 DcmDsl . . . . . . . . . . . . . . . . . . . . . . . . . 457
10.2.4.2 DcmDslBuffer . . . . . . . . . . . . . . . . . . . . . . 458
10.2.4.3 DcmDslCallbackDCMRequestService . . . . . . . . 459
10.2.4.4 DcmDslDiagResp . . . . . . . . . . . . . . . . . . . . 460
10.2.4.5 DcmDslProtocol . . . . . . . . . . . . . . . . . . . . 461
10.2.4.6 DcmDslProtocolRow . . . . . . . . . . . . . . . . . . 462
10.2.4.7 DcmDslConnection . . . . . . . . . . . . . . . . . . . 470
10.2.4.8 DcmDslMainConnection . . . . . . . . . . . . . . . . 472
10.2.4.9 DcmDslProtocolRx . . . . . . . . . . . . . . . . . . . 475
10.2.4.10 DcmDslProtocolTx . . . . . . . . . . . . . . . . . . . 477
10.2.4.11 DcmDslPeriodicTransmission . . . . . . . . . . . . . 478
10.2.4.12 DcmDslPeriodicConnection . . . . . . . . . . . . . . 479
10.2.4.13 DcmDslResponseOnEvent . . . . . . . . . . . . . . 480
10.2.5 DcmDsp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
10.2.5.1 DcmDspReadDTCInformation . . . . . . . . . . . . . 488
10.2.5.2 DcmDspReadDTCInformationUserDefinedFault-
Memory . . . . . . . . . . . . . . . . . . . . . . . . . 489
10.2.5.3 DcmDspAuthentication . . . . . . . . . . . . . . . . . 490
10.2.5.4 DcmDspAuthenticationConnection . . . . . . . . . . 494
10.2.5.5 Communication Control . . . . . . . . . . . . . . . . 501
10.2.5.5.1 DcmDspComControl . . . . . . . . . . . . . . 501
10.2.5.5.2 DcmDspComControlAllChannel . . . . . . . . 502
10.2.5.5.3 DcmDspComControlSetting . . . . . . . . . . 503
10.2.5.5.4 DcmDspComControlSpecificChannel . . . . . 504
10.2.5.5.5 DcmDspComControlSubNode . . . . . . . . . 505
10.2.5.6 DcmDspCommonAuthorization . . . . . . . . . . . . 507
10.2.5.7 DIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
10.2.5.7.1 DcmDspDid . . . . . . . . . . . . . . . . . . . 509
10.2.5.7.2 DcmDspDidInfo . . . . . . . . . . . . . . . . . 513
10.2.5.7.3 DcmDspDidRead . . . . . . . . . . . . . . . . 515
10.2.5.7.4 DcmDspDidSignal . . . . . . . . . . . . . . . . 518
10.2.5.7.5 DcmDspDidSupportInfo . . . . . . . . . . . . . 519
10.2.5.7.6 DcmDspDidRange . . . . . . . . . . . . . . . . 520
10.2.5.7.7 DcmDspDidWrite . . . . . . . . . . . . . . . . 525
10.2.5.8 DcmDspControlDTCSetting . . . . . . . . . . . . . . 528
10.2.5.9 Data elements . . . . . . . . . . . . . . . . . . . . . 530
10.2.5.9.1 DcmDspData . . . . . . . . . . . . . . . . . . . 530
10.2.5.9.2 DcmDspDiagnosisScaling . . . . . . . . . . . 545
10.2.5.9.3 DcmDspArgumentScaling . . . . . . . . . . . . 546
10.2.5.9.4 DcmDspAlternativeArgumentData . . . . . . . 547
10.2.5.9.5 DcmDspTextTableMapping . . . . . . . . . . . 548

19 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

10.2.5.9.6 DcmDspAlternativeDataInterface . . . . . . . . 549

10.2.5.9.7 DcmDspAlternativeDataType . . . . . . . . . . 550
10.2.5.9.8 DcmDspAlternativeDiagnosticDataElement . . 551
10.2.5.9.9 DcmDataElementInstance . . . . . . . . . . . 552
10.2.5.9.10DcmDspExternalSRDataElementClass . . . . 553
10.2.5.9.11DcmSubElementInDataElementInstance . . . 554
10.2.5.9.12DcmSubElementInImplDataElementInstance . 555
10.2.5.9.13DcmDspDidDataSupportInfo . . . . . . . . . . 555
10.2.5.9.14DcmDspDataInfo . . . . . . . . . . . . . . . . 556
10.2.5.10 DcmDspDidControl . . . . . . . . . . . . . . . . . . . 557
10.2.5.11 DcmDspDidControlEnableMask . . . . . . . . . . . . 563
10.2.5.12 Ecu Reset . . . . . . . . . . . . . . . . . . . . . . . . 563
10.2.5.12.1DcmDspEcuReset . . . . . . . . . . . . . . . . 563
10.2.5.12.2DcmDspEcuResetRow . . . . . . . . . . . . . 564
10.2.5.13 Memory . . . . . . . . . . . . . . . . . . . . . . . . . 565
10.2.5.13.1DcmDspMemory . . . . . . . . . . . . . . . . . 565
10.2.5.13.2DcmDspMemoryTransfer . . . . . . . . . . . . 566
10.2.5.13.3DcmDspAddressAndLengthFormatIdentifier . 567
10.2.5.13.4DcmDspMemoryIdInfo . . . . . . . . . . . . . 568
10.2.5.13.5DcmDspMemoryTransferIdInfo . . . . . . . . . 570
10.2.5.13.6DcmDspReadMemoryRangeByLabelInfo . . . 571
10.2.5.13.7DcmDspReadMemoryRangeInfo . . . . . . . . 573
10.2.5.13.8DcmDspWriteMemoryRangeByLabelInfo . . . 576
10.2.5.13.9DcmDspWriteMemoryRangeInfo . . . . . . . . 579
10.2.5.14 PIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
10.2.5.14.1DcmDspPid . . . . . . . . . . . . . . . . . . . 584
10.2.5.14.2DcmDspPidSupportInfo . . . . . . . . . . . . . 588
10.2.5.14.3DcmDspPidData . . . . . . . . . . . . . . . . . 589
10.2.5.14.4DcmDspPidService01 . . . . . . . . . . . . . . 591
10.2.5.14.5DcmDspPidService02 . . . . . . . . . . . . . . 593
10.2.5.14.6DcmDspPidDataSupportInfo . . . . . . . . . . 594
10.2.5.15 DcmDspRequestControl . . . . . . . . . . . . . . . . 595
10.2.5.16 DcmDspRequestFileTransfer . . . . . . . . . . . . . 597
10.2.5.17 Response on Event . . . . . . . . . . . . . . . . . . . 599
10.2.5.17.1DcmDspRoe . . . . . . . . . . . . . . . . . . . 599
10.2.5.17.2DcmDspRoeEvent . . . . . . . . . . . . . . . . 601
10.2.5.17.3DcmDspRoeEventProperties . . . . . . . . . . 603
10.2.5.17.4DcmDspRoeOnChangeOfDataIdentifier . . . . 603
10.2.5.17.5DcmDspRoeOnDTCStatusChange . . . . . . 604
10.2.5.17.6DcmDspRoeEventWindowTime . . . . . . . . 604
10.2.5.18 Routines . . . . . . . . . . . . . . . . . . . . . . . . . 606
10.2.5.18.1DcmDspRoutine . . . . . . . . . . . . . . . . . 606
10.2.5.18.2DcmDspRequestRoutineResults . . . . . . . . 608
10.2.5.18.3DcmDspRequestRoutineResultsIn . . . . . . . 612
10.2.5.18.4DcmDspRequestRoutineResultsInSignal . . . 613
10.2.5.18.5DcmDspRequestRoutineResultsOut . . . . . . 615

20 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

10.2.5.18.6DcmDspRequestRoutineResultsOutSignal . . 616
10.2.5.18.7DcmDspStartRoutine . . . . . . . . . . . . . . 618
10.2.5.18.8DcmDspStartRoutineIn . . . . . . . . . . . . . 622
10.2.5.18.9DcmDspStartRoutineInSignal . . . . . . . . . 624
10.2.5.18.10
DcmDspStartRoutineOut . . . . . . . . . . . . 627
10.2.5.18.11
DcmDspStartRoutineOutSignal . . . . . . . . 628
10.2.5.18.12
DcmDspStopRoutine . . . . . . . . . . . . . . 631
10.2.5.18.13
DcmDspStopRoutineIn . . . . . . . . . . . . . 635
10.2.5.18.14
DcmDspStopRoutineInSignal . . . . . . . . . . 637
10.2.5.18.15
DcmDspStopRoutineOut . . . . . . . . . . . . 640
10.2.5.18.16
DcmDspStopRoutineOutSignal . . . . . . . . . 641
10.2.5.19 Session Security and Modes . . . . . . . . . . . . . 644
10.2.5.19.1DcmDspSecurity . . . . . . . . . . . . . . . . . 644
10.2.5.19.2DcmDspSecurityRow . . . . . . . . . . . . . . 646
10.2.5.19.3DcmDspSession . . . . . . . . . . . . . . . . . 652
10.2.5.19.4DcmDspSessionRow . . . . . . . . . . . . . . 654
10.2.5.19.5DcmModeCondition . . . . . . . . . . . . . . . 656
10.2.5.19.6DcmSwcDataElementValue . . . . . . . . . . . 660
10.2.5.19.7DcmSwcDataElementPrimitive . . . . . . . . . 660
10.2.5.19.8DcmSwcDataElementArray . . . . . . . . . . . 660
10.2.5.19.9DcmSwcDataElementArrayElement . . . . . . 661
10.2.5.19.10
DcmModeRule . . . . . . . . . . . . . . . . . . 662
10.2.5.20 DcmDspVehInfo . . . . . . . . . . . . . . . . . . . . 664
10.2.5.21 DcmDspVehInfoData . . . . . . . . . . . . . . . . . . 666
10.2.5.22 DcmDspPeriodicTransmission . . . . . . . . . . . . . 668
10.2.5.23 DcmDspClearDTC . . . . . . . . . . . . . . . . . . . 673
10.2.6 DcmGeneral . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
10.2.6.1 DcmSecurityEventRefs . . . . . . . . . . . . . . . . 680
10.3 Protocol Configuration Example . . . . . . . . . . . . . . . . . . . . . . 695
10.4 Published Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
A Not applicable requirements 696

21 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

1 Introduction and functional overview

The Dcm SWS describes the functionality, the API, and the configuration of the
AUTOSAR Basic Software module Dcm (Diagnostic Communication Manager). The
Dcm module provides a common API for diagnostic services. The functionality of the
Dcm module is used by external diagnostic tools during the development, manufactur-
ing or service.

Offboard Onboard

AUTOSAR Application

DCM*
Manufacturing
Microcontroller (µC)

Development

Diagnostic
Tool
Service
*DCM: Diagnostic Communication Manager

Figure 1.1: Overview of the communication between the external diagnostic tools and
the onboard AUTOSAR Application

The Dcm module ensures diagnostic data flow and manages the diagnostic states, es-
pecially diagnostic sessions and security states. Furthermore, the Dcm module checks
if the diagnostic service request is supported and if the service may be executed in
the current session according to the diagnostic states.The Dcm module provides the
OSI-Layers 5 to 7 of Table 1: Diagnostic protocols and OSI-Layer.
OSI-
Protocols
Layer
Legislated
OBD -
7 UDS-Protocol -
ISO15031-5
ISO14229-1 [1]
[2]
6 - - - - -
5 ISO15765-3 - - - ISO 15765-4
4 ISO15765-2 - - - -
3 ISO15765-2 - - - ISO 15765-4
CAN-
2 LIN-Protocol FlexRay MOST ISO 15765-4
Protocol
CAN-
1 LIN-Protocol FlexRay MOST ISO 15765-4
Protocol

Table 1.1: Diagnostic protocols and OSI-Layers

At OSI-level 7, the Dcm module provides an extensive set of ISO14229-1 [1] services.
In addition, the Dcm module provides mechanisms to support the OBD services $01 -

22 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

$0A defined in documents [3, SAE J1979] and [2, ISO 15031-5]. With these services,
Autosar OBD functionality is capable of meeting all light duty OBD regulations worldwide
(California OBDII, EOBD, Japan OBD, and all others). At OSI-level 5, the Dcm module
handles the network-independent sections of the following specifications:
• ISO15765-3 [4]: Implementation of unified diagnostic services (UDS on CAN)
• ISO15765-4 [5]: Requirements for emission-related systems, Chapter 5 ”Session
Layer”
In the AUTOSAR Architecture the Diagnostic Communication Manager is located in the
Communication Services (Service Layer).

Figure 1.2: Position of the Dcm module in AUTOSAR Architecture

The Dcm module is network-independent. All network-specific functionality (the

specifics of networks like CAN, LIN, FlexRay or MOST) is handled outside of the Dcm
module. The PDU Router (PduR) module provides a network-independent interface
to the Dcm module. The Dcm module receives a diagnostic message from the PduR
module. The Dcm module processes and checks internally the diagnostic message.
As part of processing the requested diagnostic service, the Dcm will interact with other
BSW modules or with SW-Components (through the RTE) to obtain requested data or
to execute requested commands. This processing is very service-specific. Typically,
the Dcm will assemble the gathered information and send a message back through the
PduR module.

23 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

2 Acronyms and Abbreviations

The glossary below includes acronyms and abbreviations relevant to the <MOD-
ULE_NAME> module that are not included in the [6, AUTOSAR glossary].
Abbreviation / Acronym: Description:
Application Layer The Application Layer is placed above the RTE. Within the Appli-
cation Layer the AUTOSAR Software-Components are placed.
Atomic Sender/Receiver inter- An atomic sender-receiver interface can be used to group DID
face data elements into one record data element prototype. All data
elements can be read or write having a single read or write oper-
ation.
Channel A link at which a data transfer can take place. If there is more
than one Channel, there is normally some kind of ID assigned to
the Channel.
Concurrent TesterPresent A UDS service TesterPresent with set suppressPosRspMsgIndi-
cationBit (3E 80) which is received with functional addressing. It
is also known as keep-alive logic..
Diagnostic Channel A link at which a data transfer between a diagnostic tool and
an ECU can take place. Example: An ECU is connected via
CAN and the diagnostic channel has an assigned CAN-ID. Diag-
nostic channels connected to other bus-systems such as MOST,
FlexRay, LIN, etc. are also possible.
External Diagnostic Tool A device which is NOT permanently connected to the vehicle
communication network. This External Diagnostic Tool can be
connected to the vehicle for various purposes, as e.g. for:
• development
• manufacturing
• service (in a garage)
Example External Diagnostic Tools are:
• a diagnostic tester
• an OBD scan tool
The External Diagnostic Tool is to be connected by a mechanic
to gather information from ”inside” the car.
Freeze Frame A set of the vehicle/system operation conditions at a specific time.
Functional Addressing The diagnostic communication model where a group or all nodes
of a specific communication network receive a message from one
sending node (1-n communication). This model is also referred
to as ’broadcast’ or ’multicast’. OBD communication will always
be done in the Functional Addressing mode.
Internal Diagnostic Tool A device/ECU which is connected to the vehicle communication
network. The Internal Diagnostic Tool can be used for:
• advanced event tracking
• advanced analysis
• for service
The behavior of the Internal Diagnostic Tool can be the same as
of an External Diagnostic Tool. The notion of ”Internal Diagnos-
tic Tool” does not imply that it is included in each ECU as an
AUTOSAR Software-Component.

24 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Abbreviation / Acronym: Description:

Physical Addressing The diagnostic communication model where a node of a specific
communication network receives a message from one sending
node (1-1 communication). This model is also referred to as ’uni-
cast’.
UDS Service this refers to a UDS Service as defined in ISO14229-1 [1].
OBD Service This refers to an OBD Service as defined in ISO15031-5 [2].
AddressAndLengthFormat Defines the number of bytes used for the memoryAddress and
Identifier memorySize parameter in the request messages.
OBD Scan tool See definition External Diagnostic Tool.
periodic transmission rate Time interval value that defines the time between two calls of a
periodic data identifier transmission. The value is configuration
specific and there are separate values for fast, medium and slow
periodic data transmission. The configured value is always an
integer multiple of the Dcm main task time.

Terms: Description:
API Application Programming Interface
CAN Controller Area Network
CEMR ControlEnableMaskRecord
Dcm Diagnostic Communication Manager
Dem Diagnostic Event Manager
Det Default Error Tracer
DID Data Identifier
DSD Diagnostic Service Dispatcher (submodule of the Dcm module)
DSL Diagnostic Session Layer (submodule of the Dcm module)
DSP Diagnostic Service Processing (submodule of the Dcm module)
DTC Diagnostic Trouble Codes
ID Identifier
LIN Local Interconnect Network
MCU Micro-Controller Unit
MOST Media Orientated System Transport
NRC Negative Response Code
OBD On-Board Diagnosis
OSI Open Systems Interconnection
PDID Periodic Data Identifier, periodically send by the Dcm after a re-
quest of ReadDataByPeriodicIndentifer
PDU Protocol Data Unit
PID Parameter Identifier
RCRRP Response correctly received - response pending
RID Routine Identifier
ROE ResponseOnEvent
RTE Runtime Environment
SAP Service Access Point
SDU Service Data Unit
SID Service Identifier
SW-C Software-Component
TP Transport Protocol
UDS Unified Diagnostic Services
Xxx_ Placeholder for an API provider
SPRMIB suppressPosRspMsgIndicationBit

25 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

2.1 Typographical Conventions

This document uses the following typographical conventions:
• see configuration parameter myConfigurationParameter: this is a reference to a
configuration parameter which can be found in Chapter 10.
• myFunction(): this is a function provided or required by the module as defined in
Chapter 8

3 Related documentation

3.1 Input documents & related standards and norms

[1] Unified diagnostic services (UDS) – Part 1: Specification and requirements (Re-
lease 2013-03)
http://www.iso.org
[2] Road vehicles – Communication between vehicle and external equipment for
emission-related diagnostic – Part 5: Emission-related diagnostic services.
http://www.iso.org
[3] SAE J1979
[4] Diagnostics on controller area network (CAN) – Part 3: Implementation of unified
diagnostic services (UDS on CAN) (Release 2004 10-06)
[5] Diagnostics on controller area network (CAN) – Part 4: Requirements for
emission-related systems (Release 2005 01-04)
[6] Glossary
AUTOSAR_TR_Glossary
[7] General Specification of Basic Software Modules
AUTOSAR_SWS_BSWGeneral
[8] General Requirements on Basic Software Modules
AUTOSAR_SRS_BSWGeneral
[9] ISO 17356-3: Road vehicles – Open interface for embedded automotive applica-
tions – Part 3: OSEK/VDX Operating System (OS)
[10] Unified diagnostic services (UDS) - Part 2: Session layer services (Release 2013-
03)
http://www.iso.org
[11] Specification of PDU Router
AUTOSAR_SWS_PDURouter
[12] Road vehicles – Diagnostics on Controller Area Networks (CAN) – Part2: Network

26 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

layer services
[13] Specification of Diagnostic Event Manager
AUTOSAR_SWS_DiagnosticEventManager
[14] Road vehicles – Communication between vehicle and external equipment for
emission-related diagnostic – Part 6: Diagnostic trouble code definitions
http://www.iso.org
[15] Specification of NVRAM Manager
AUTOSAR_SWS_NVRAMManager
[16] Specification of Crypto Service Manager
AUTOSAR_SWS_CryptoServiceManager
[17] Specification of Key Manager
AUTOSAR_SWS_KeyManager
[18] Specification of I/O Hardware Abstraction
AUTOSAR_SWS_IOHardwareAbstraction

3.2 Related specification

AUTOSAR provides a General Specification on Basic Software modules [7, SWS BSW
General] , which is also valid for Diagnostic Communication Manager.
Thus, the specification SWS BSW General shall be considered as additional and re-
quired specification for Diagnostic Communication Manager.

4 Constraints and assumptions

4.1 Limitations
The following limitations apply when using the Dcm module:
• The Dcm module does not provide any diagnostic multi-channel capabilities. This
means that parallel requests of a tester addressed to different independent func-
tionalities cannot be processed by a single Dcm module. Furthermore, the con-
cept currently implemented does not take more than one instance of a Dcm mod-
ule residing in one ECU into account. As the legislator requires that emission-
related service requests according to ISO 15031-5 [2] shall be processed prior to
any enhanced diagnostic requests, the Dcm module provides a protocol switching
mechanism based on protocol prioritization.
• UDS Service AccessTimingParameter (0x83) is not supported by the ISO stan-
dards in CAN and LIN. Also it is not planned to support this service with FlexRay.
Therefore no support for this service is planned.

27 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• Subfunction onComparisionOfValues of Service ResponseOnEvent is not sup-

ported in the current release.
• Subfunction onTimerInterrupt of Service ResponseOnEvent is not supported in
the current release.
• UDS Service SecuredDataTransmission (0x84) is not supported in the current
release.
• The Dcm SWS does not cover any SAE J1939 related diagnostic requirements.
• Due to DEM limitation, the diagnostic service $19 05 is limited to the OBD leg-
islative freeze frame.
• Management of IOControl service without InputOutputControlParameter in re-
quest and response is not supported
• The length of controlState parameter in IOControl request and response has to be
of same size (due to the one configuration parameter DcmDspDataByteSize)
• Same layout of a DID which is used in RDBI, WDBI or IOCBI services
• The user optional parameter DTCSettingControlOptionRecord in the Con-
trolDTCSetting request is only supported if it corresponds to a groupOfAllDTCs
(0xFFFFFF) value. In other cases it has to be managed in a vendor specific
implementation.
• Only the ControlDTCSetting sub-functions 0x01 and 0x02 are supported.
• The handling of infrastructure errors reported by the RTE during DCM/DEM <-
> SW-C interactions is missing from the SWS and might have to be taken into
account by implementers if they need it.
• The Dcm does not support DLT for ROE
• The ROE ServiceToRespondTo does not support PageBuffering
• ROE only supports sub-function listed in Table 2
• DID range feature cannot be applied for services DynamicallyDefineDataIdenti-
fier, ReadDataByPeriodicIdentifier and InputOutputControlById
• AUTOSAR Dcm is not intended to be used in the bootloader
• PeriodicTransmission is not possible on FlexRay, as ISO 14229-4 demands
header information (address information (source and target address) and FPL
(Frame Payload length)). This information can’t be filled with the specified con-
cept of IF interface.
• The specification of the transformer for intra ecu communication between the Dcm
module and the NvBlockSoftwareComponentType is not standardized in the cur-
rent AUTOSAR release. For this scenario custom transformers implemented by
a complex driver can be used. To elaborate on this the responsible stakeholder
(usually the OEM) needs to specify the custom transformer from a behavioral

28 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

point of view in a separate document (this might include definition of byte-ordering

or alignment). If there is the necessity to define transformer specific attributes in
the model this can be done using special data groups in UserDefinedTransforma-
tionDescription and UserDefinedTransformationISignalProps. For the configura-
tion of this scenario, a DataPrototypeMapping shall exist for the affected Sender-
ReceiverInterfaces of the Dcm module and the NvBlockSoftwareComponentType
which refers to a DataTransformation in the role firstToSecondDataTransforma-
tion. This DataTransformation shall reference exactly one TransformationTech-
nology in the role transformerChain with the transformerClass attribute set to "se-
rializer" and may compose a UserDefinedTransformationDescription in the role
transformationDescription.
• In certain situations the Dcm module is capable to process diagnostic requests
in parallel. This possibility is explicitly limited of OBD in parallel to UDS protocol
processing. No other protocol combination can be processed in parallel. Particu-
larly the use case of parallel processing of two or more UDS protocol requests or
WWH-OBD and UDS protocols is not supported.
• For UDS service 0x29, the Dcm supports only the sub-functions for PKI. Authen-
tication via challenge response is not supported.
• For UDS service 0x29, secure diagnostic communication with Diffie-Hellmann
key exchange is not supported.
• For UDS service 0x29 the Dcm does not support NRC ’Certificate verification failed
- Invalid Content’.

4.2 Applicability to car domains

The Dcm module can be used for all car domains.

4.3 Applicability to emission-related environments (OBD)

This Dcm SWS is intended to fulfill the emission related requirements given by legisla-
tor. However, the supplier of the emission related system is responsible to fulfill the
OBD requirements. Certain requirements cannot be fulfilled by the Dcm module by itself,
but need to be considered at the level of the entire ECU or system. Example: During
the integration of the Dcm module within the system, the timing requirements (50ms
response time) must be fulfilled.
For WWH-OBD only the FunctionalGroupIdentifier 0x33 is currently supported.

29 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

5 Dependencies to other modules

The AUTOSAR Diagnostic Communication Manager (DCM) has interfaces and depen-
dencies to the following Basic Software modules and SW-Cs:

          


         

InfotypeServices ServiceRequestNotification

SecurityAccess RoutineServices
«abswRequires» «abswRequires»

«abswRequires»
DataServices «abswRequires» CallbackDCMRequestServices
«abswRequires»

«abswRequires» RequestManufacturerNotification «abswRequires»

DataServices_DIDRange SecurityAccess ServiceRequestSupplierNotification
DataServicesPIDRPort InfotypeServices RoutineServices RequestControlServices
CallbackDCMRequestServices
«abswRequires»
Dcm «abswRequires»
DataServices_DIDRange
RequestControlServices

Dem
«realize» «optional»
Dem_DcmReadDataOfOBDFreezeFrame «realize»
Dcm_MainFunction

«realize»
Dcm_Init NvM

«realize»
«optional» NvM_WriteBlock

«optional»
IoHwAb
«realize»
IoHwAb_Dcm «realize» «realize» «mandatory»

BswM
«realize» «optional»
BswM_Dcm_ApplicationUpdated

PduR_General Dcm_PduR Dcm_ComM ComM_Types

ComM_Dcm
«realize» «optional»
BswM_Dcm_CommunicationMode_CurrentState «mandatory» «realize» «realize»

PduR ComM

Figure 5.1: Interaction of the Dcm with other modules

• Diagnostic Event Manager (DEM): The DEM module provides function to retrieve
all information related to fault memory such that the Dcm module is able to re-
spond to tester requests by reading data from the fault memory.
• Protocol Data Unit Router (PduR module): The PduR module provides functions
to transmit and receive diagnostic data. Proper operation of the Dcm module
presumes that the PduR interface supports all service primitives defined for the
Service Access Point (SAP) between diagnostic application layer and underlying
transport layer (see ISO14229-1 [1], chapter 5 Application layer services).
• Communication Manager (ComM): The ComM module provides functions such
that the Dcm module can indicate the states ”active” and ”inactive” for diagnostic

30 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

communication. The Dcm module provides functionality to handle the commu-

nication requirements ”Full-/ Silent-/ No-Communication”. Additionally, the Dcm
module provides the functionality to enable and disable Diagnostic Communica-
tion if requested by the ComM module.
• SW-C and RTE: The Dcm module has the capability to analyze the received di-
agnostic request data stream and handles all functionalities related to diagnostic
communication such as protocol handling and timing. Based on the analysis of
the request data stream the Dcm module assembles the response data stream
and delegates routines or IO-Control executions to SW-Cs .If any of the data el-
ements or functional states cannot be provided by the Dcm module itself the Dcm
requests data or functional states from SW-Cs via port-interfaces or from other
BSW modules through direct function-calls.
• BswM: The Dcm notifies the BswM that the application was updated if the initial-
ization of the Dcm is the consequence of a jump from the bootloader . The Dcm
also indicates to the BswM a communication mode change.
• Crypto Service Manager (Csm): The crypto service module provides a wide
range of cryptographic algorithms. The Csm is used for authentication calcu-
lation.
• Key Manager (KeyM): The key manager module provides support for certificate
handling and APIs to realize authenticated diagnostics via certificates.

6 Requirements Tracing
The following tables reference the requirements specified in
AUTOSAR_RS_RSDiagnostics as well as [8] and links to the fulfillment of these.
Please note that if column “Satisfied by” is empty for a specific requirement this means
that this requirement is not fulfilled by this document.
Requirement Description Satisfied by
[RS_Diag_04002] The Diagnostic event (fault) [SWS_Dcm_NA_00999]
management shall be
established as Basic SW Module
[RS_Diag_04003] Network independent design [SWS_Dcm_00030]
[RS_Diag_04005] Manage Security Access level [SWS_Dcm_00020] [SWS_Dcm_00033]
handling [SWS_Dcm_00252] [SWS_Dcm_00338]
[SWS_Dcm_01397] [SWS_Dcm_01535]
[SWS_Dcm_CONSTR_6083]
[RS_Diag_04006] Manage session handling [SWS_Dcm_00022] [SWS_Dcm_00250]
[SWS_Dcm_00339] [SWS_Dcm_01373]
[SWS_Dcm_01374] [SWS_Dcm_01375]
[SWS_Dcm_01376] [SWS_Dcm_01377]
[SWS_Dcm_01378] [SWS_Dcm_01535]

31 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Requirement Description Satisfied by

[RS_Diag_04007] Provide a diagnostic service [SWS_Dcm_NA_00999]
handling for the applications
involved in diagnostic
functionality
[RS_Diag_04011] Provide diagnostic state [SWS_Dcm_00338] [SWS_Dcm_00339]
information to applications [SWS_Dcm_00340] [SWS_Dcm_01321]
[SWS_Dcm_01322]
[RS_Diag_04015] Timing handling according to [SWS_Dcm_00027] [SWS_Dcm_00030]
ISO14229-2 [SWS_Dcm_00143] [SWS_Dcm_00144]
[RS_Diag_04016] Support ”Busy handling” by [SWS_Dcm_00024]
sending a negative response
0x78
[RS_Diag_04019] Provide confirmation after [SWS_Dcm_NA_00999]
transmit diagnostic responses to
the application
[RS_Diag_04020] Suppress responses to [SWS_Dcm_00001] [SWS_Dcm_00200]
diagnostic tool requests
[RS_Diag_04021] Handling of different diagnostic [SWS_Dcm_00015]
sessions in parallel
[RS_Diag_04024] Access and handle specific data [SWS_Dcm_NA_00999]
elements and data element
groups if requested by an
external scan tool
[RS_Diag_04031] Notify the Function Inhibition [SWS_Dcm_NA_00999]
Manager (FIM) upon changes of
the event status in order to
process them according to the
SW components dependencies
[RS_Diag_04032] Different diagnostic addresses [SWS_Dcm_NA_00999]
shall be supported by multiple
(physical) channels
[RS_Diag_04033] Support the upload/download [SWS_Dcm_00496] [SWS_Dcm_00499]
services for reading/writing data [SWS_Dcm_00502] [SWS_Dcm_00503]
in an ECU in an extended and [SWS_Dcm_00504] [SWS_Dcm_00505]
manufacturer specific diagnostic [SWS_Dcm_01417] [SWS_Dcm_01418]
session [SWS_Dcm_01419] [SWS_Dcm_01420]
[SWS_Dcm_01421] [SWS_Dcm_01422]
[RS_Diag_04057] Classification of events for [SWS_Dcm_NA_00999]
series production, OBD and
expert usage
[RS_Diag_04058] Ability to access different event [SWS_Dcm_00004] [SWS_Dcm_00005]
memories [SWS_Dcm_00077] [SWS_Dcm_00279]
[SWS_Dcm_00293] [SWS_Dcm_00295]
[SWS_Dcm_00378] [SWS_Dcm_00383]
[SWS_Dcm_00384] [SWS_Dcm_00388]
[SWS_Dcm_00389] [SWS_Dcm_00393]
[SWS_Dcm_00465] [SWS_Dcm_01147]
[SWS_Dcm_01263]
[RS_Diag_04059] Configuration of timing [SWS_Dcm_NA_00999]
parameters

32 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Requirement Description Satisfied by

[RS_Diag_04063] Process a dedicated event [SWS_Dcm_NA_00999]
identifier for each monitoring
path to support an autonomous
handling of different events/
faults
[RS_Diag_04064] Provide configurable buffer sizes [SWS_Dcm_NA_00999]
for storage of the events, status
information and environmental
data
[RS_Diag_04067] Provide the diagnostic status [SWS_Dcm_00293] [SWS_Dcm_00378]
information according to ISO
14229-1
[RS_Diag_04068] The diagnostic in AUTOSAR [SWS_Dcm_NA_00999]
shall support event specific
debounce counters to improve
signal quality internally
(According to ISO 14229-1
Appendix D)
[RS_Diag_04071] Process events according to [SWS_Dcm_NA_00999]
their defined importance like
priority and/or severity
[RS_Diag_04077] Uses standard mechanisms [SWS_Dcm_NA_00999]
provided by persistency modules
[RS_Diag_04085] No description [SWS_Dcm_NA_00999]
[RS_Diag_04086] No description [SWS_Dcm_NA_00999]
[RS_Diag_04087] No description [SWS_Dcm_NA_00999]
[RS_Diag_04089] No description [SWS_Dcm_NA_00999]
[RS_Diag_04090] No description [SWS_Dcm_NA_00999]
[RS_Diag_04091] Notification about valid freeze [SWS_Dcm_NA_00999]
frame data to applications
[RS_Diag_04093] Memory overflow indication [SWS_Dcm_NA_00999]
[RS_Diag_04097] Decentralized and modular [SWS_Dcm_NA_00999]
diagnostic configuration in
applications
[RS_Diag_04098] Interact with standard bootloader [SWS_Dcm_00532] [SWS_Dcm_00535]
[SWS_Dcm_00536] [SWS_Dcm_00592]
[SWS_Dcm_00654] [SWS_Dcm_00767]
[SWS_Dcm_01163] [SWS_Dcm_01177]
[SWS_Dcm_01423] [SWS_Dcm_01424]
[SWS_Dcm_01425]
[SWS_Dcm_CONSTR_6080]
[RS_Diag_04100] No description [SWS_Dcm_NA_00999]
[RS_Diag_04101] No description [SWS_Dcm_NA_00999]
[RS_Diag_04105] Event memory management [SWS_Dcm_NA_00999]
[RS_Diag_04107] Provide defensive behavior [SWS_Dcm_NA_00999]
[RS_Diag_04109] Provide an interface to retrieve [SWS_Dcm_NA_00999]
the number of event memory
entries
[RS_Diag_04110] SAE J1939 lamp status [SWS_Dcm_NA_00999]
[RS_Diag_04111] SAE J1939 Expanded-Freeze [SWS_Dcm_NA_00999]
Frame
[RS_Diag_04112] The DEM module shall support [SWS_Dcm_NA_00999]
DTCs according to SAE J1939

33 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Requirement Description Satisfied by

[RS_Diag_04113] Support a set of SAE J1939 [SWS_Dcm_NA_00999]
DM-messages
[RS_Diag_04115] The optional parameter [SWS_Dcm_00406] [SWS_Dcm_01063]
DTCSettingControlOption
Record as part of UDS service
ControlDTCSetting shall be
limited to GroupOfDTC
[RS_Diag_04117] Configurable behavior for DTC [SWS_Dcm_NA_00999]
deletion
[RS_Diag_04118] Optionally support event [SWS_Dcm_NA_00999]
displacement
[RS_Diag_04119] Handle the execution of [SWS_Dcm_00628] [SWS_Dcm_00858]
diagnostic services according to [SWS_Dcm_00859] [SWS_Dcm_01435]
the assigned diagnostic session [SWS_Dcm_NA_00999]
[RS_Diag_04120] Support a predefined Address [SWS_Dcm_NA_00999]
AndLengthFormatIdentifier
[RS_Diag_04121] Provide the handling of service [SWS_Dcm_NA_00999]
DynamicallyDefineDataIdentifier
according to ISO 14229-1
[RS_Diag_04123] Harmonized Driving//WarmUp [SWS_Dcm_NA_00999]
cycles
[RS_Diag_04124] Store the current debounce [SWS_Dcm_NA_00999]
counter value non-volatile to
over a power-down cycle
[RS_Diag_04125] Event debounce counter shall be [SWS_Dcm_NA_00999]
configurable
[RS_Diag_04126] Configurable suppression of [SWS_Dcm_NA_00999]
events
[RS_Diag_04127] Configurable record numbers [SWS_Dcm_NA_00999]
and trigger options for
DTCSnapshotRecords and
DTCExtendedDataRecords
[RS_Diag_04129] Provide OBD-specific [SWS_Dcm_NA_00999]
configuration capabilities
[RS_Diag_04131] Consistent event management [SWS_Dcm_NA_00999]
mechanisms
[RS_Diag_04133] Aging for event memory entries [SWS_Dcm_NA_00999]
[RS_Diag_04135] Support UDS service $38 [SWS_Dcm_NA_00999]
(RequestFileTransfer)
[RS_Diag_04136] Configurable ”confirmed” [SWS_Dcm_NA_00999]
threshold
[RS_Diag_04137] Definition of replacement failure [SWS_Dcm_NA_00999]
[RS_Diag_04139] Support subfunction 0x42 of [SWS_Dcm_NA_00999]
UDS service 0x19
[RS_Diag_04140] Aging for UDS status bits [SWS_Dcm_NA_00999]
”confirmedDTC” and ”testFailed
SinceLastClear”
[RS_Diag_04143] No description [SWS_Dcm_NA_00999]
[RS_Diag_04144] No description [SWS_Dcm_NA_00999]
[RS_Diag_04145] No description [SWS_Dcm_NA_00999]
[RS_Diag_04146] No description [SWS_Dcm_NA_00999]
[RS_Diag_04147] Communication with the [SWS_Dcm_00642] [SWS_Dcm_01186]
transport layers to receive and
send diagnostic data

34 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Requirement Description Satisfied by

[RS_Diag_04148] Provide capabilities to inform [SWS_Dcm_NA_00999]
applications about diagnostic
data changes
[RS_Diag_04150] Support the primary fault [SWS_Dcm_NA_00999]
memory defined by ISO 14229-1
[RS_Diag_04151] Event status handling [SWS_Dcm_NA_00999]
[RS_Diag_04153] Support generic connections [SWS_Dcm_00849] [SWS_Dcm_01347]
[SWS_Dcm_01348]
[RS_Diag_04159] Control of DTC storage [SWS_Dcm_00249] [SWS_Dcm_01399]
[RS_Diag_04162] Parallel fault memory access [SWS_Dcm_01369] [SWS_Dcm_01370]
[SWS_Dcm_01371] [SWS_Dcm_01372]
[RS_Diag_04163] Parallel OBD and UDS [SWS_Dcm_01365] [SWS_Dcm_01366]
processing [SWS_Dcm_01367]
[RS_Diag_04215] Support of UDS service Read [SWS_Dcm_00716] [SWS_Dcm_00721]
DataByPeriodicIdentifier (0x2A) [SWS_Dcm_00722] [SWS_Dcm_00820]
[SWS_Dcm_00843] [SWS_Dcm_00851]
[SWS_Dcm_01093] [SWS_Dcm_01094]
[SWS_Dcm_01095] [SWS_Dcm_01096]
[SWS_Dcm_01097] [SWS_Dcm_01098]
[SWS_Dcm_01099] [SWS_Dcm_01100]
[SWS_Dcm_01101] [SWS_Dcm_01103]
[SWS_Dcm_01104] [SWS_Dcm_01105]
[SWS_Dcm_01106] [SWS_Dcm_01107]
[SWS_Dcm_01108] [SWS_Dcm_01109]
[SWS_Dcm_01110] [SWS_Dcm_01111]
[SWS_Dcm_01112] [SWS_Dcm_01115]
[SWS_Dcm_01117] [SWS_Dcm_01118]
[SWS_Dcm_01426] [SWS_Dcm_01427]
[SWS_Dcm_01428] [SWS_Dcm_01568]
[SWS_Dcm_01569] [SWS_Dcm_01570]
[SWS_Dcm_01571] [SWS_Dcm_01572]
[SWS_Dcm_01573] [SWS_Dcm_01574]
[SWS_Dcm_01575] [SWS_Dcm_01576]
[SWS_Dcm_01577] [SWS_Dcm_01578]
[RS_Diag_04218] Support of UDS service 0x2F [SWS_Dcm_00256] [SWS_Dcm_00396]
InputOutputControlByIDentifier [SWS_Dcm_00397] [SWS_Dcm_00398]
[SWS_Dcm_00399] [SWS_Dcm_00563]
[SWS_Dcm_00564] [SWS_Dcm_00565]
[SWS_Dcm_00579] [SWS_Dcm_00580]
[SWS_Dcm_00581] [SWS_Dcm_00640]
[SWS_Dcm_00680] [SWS_Dcm_00682]
[SWS_Dcm_01273] [SWS_Dcm_01274]
[SWS_Dcm_01275] [SWS_Dcm_01277]
[SWS_Dcm_01313] [SWS_Dcm_01434]
[SWS_Dcm_01436] [SWS_Dcm_01437]
[SWS_Dcm_01438] [SWS_Dcm_01439]
[SWS_Dcm_01440] [SWS_Dcm_01441]
[SWS_Dcm_01554] [SWS_Dcm_91057]
[SWS_Dcm_91058] [SWS_Dcm_91059]
[SWS_Dcm_91060] [SWS_Dcm_91061]
[SWS_Dcm_CONSTR_6084]
[SWS_Dcm_CONSTR_6085]
[SWS_Dcm_CONSTR_6086]

35 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Requirement Description Satisfied by

[RS_Diag_04224] Support the UDS service 0x31 [SWS_Dcm_01442] [SWS_Dcm_01443]
(RoutineControl) according to [SWS_Dcm_01580] [SWS_Dcm_01581]
ISO 14229-1
[RS_Diag_04230] Support of UDS service 0x29 [SWS_Dcm_01459] [SWS_Dcm_01460]
(Authentication) [SWS_Dcm_01461] [SWS_Dcm_01463]
[SWS_Dcm_01464] [SWS_Dcm_01465]
[SWS_Dcm_01466] [SWS_Dcm_01467]
[SWS_Dcm_01468] [SWS_Dcm_01469]
[SWS_Dcm_01477] [SWS_Dcm_01478]
[SWS_Dcm_01479] [SWS_Dcm_01480]
[SWS_Dcm_01481] [SWS_Dcm_01482]
[SWS_Dcm_01483] [SWS_Dcm_01484]
[SWS_Dcm_01485] [SWS_Dcm_01486]
[SWS_Dcm_01487] [SWS_Dcm_01488]
[SWS_Dcm_01489] [SWS_Dcm_01493]
[SWS_Dcm_01503] [SWS_Dcm_01504]
[SWS_Dcm_01506] [SWS_Dcm_01507]
[SWS_Dcm_01508] [SWS_Dcm_01509]
[SWS_Dcm_01510] [SWS_Dcm_01511]
[SWS_Dcm_01512] [SWS_Dcm_01513]
[SWS_Dcm_01515] [SWS_Dcm_01518]
[SWS_Dcm_01528] [SWS_Dcm_01529]
[SWS_Dcm_01530] [SWS_Dcm_01532]
[SWS_Dcm_01533] [SWS_Dcm_01534]
[SWS_Dcm_01535] [SWS_Dcm_01536]
[SWS_Dcm_01537] [SWS_Dcm_01538]
[SWS_Dcm_01542] [SWS_Dcm_01544]
[SWS_Dcm_01551] [SWS_Dcm_01558]
[SWS_Dcm_01559] [SWS_Dcm_01560]
[SWS_Dcm_01561] [SWS_Dcm_01565]
[SWS_Dcm_01579] [SWS_Dcm_01588]
[SWS_Dcm_CONSTR_6094]
[SWS_Dcm_CONSTR_6096]
[RS_Diag_04232] Access rights in client [SWS_Dcm_01516]
certificates [SWS_Dcm_CONSTR_6087]
[SWS_Dcm_CONSTR_6089]
[RS_Diag_04233] Access granularity of diagnostic [SWS_Dcm_01496] [SWS_Dcm_01514]
services [SWS_Dcm_01539] [SWS_Dcm_01540]
[SWS_Dcm_01541] [SWS_Dcm_01545]
[SWS_Dcm_01546] [SWS_Dcm_01547]
[SWS_Dcm_01548] [SWS_Dcm_01549]
[SWS_Dcm_01552] [SWS_Dcm_01553]
[SWS_Dcm_01555] [SWS_Dcm_01556]
[SWS_Dcm_01557] [SWS_Dcm_01562]
[SWS_Dcm_CONSTR_6088]
[RS_Diag_04233; No description [SWS_Dcm_01522] [SWS_Dcm_01523]
RS_Diag_04234] [SWS_Dcm_01524] [SWS_Dcm_01525]
[SWS_Dcm_01526] [SWS_Dcm_01527]
[RS_Diag_04234] Binary compatibility of white list [SWS_Dcm_01521]
for individual access
[RS_Diag_04235] Client certificate validity [SWS_Dcm_01470] [SWS_Dcm_01471]
[SWS_Dcm_01472] [SWS_Dcm_01473]
[SWS_Dcm_01474] [SWS_Dcm_01475]
[SWS_Dcm_01476]

36 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Requirement Description Satisfied by

[RS_Diag_04236] Client certificate target [SWS_Dcm_01490] [SWS_Dcm_01491]
identification [SWS_Dcm_01492]
[RS_Diag_04243] Update of constant parameters [SWS_Dcm_01582] [SWS_Dcm_01583]
through diagnostics [SWS_Dcm_01584] [SWS_Dcm_01585]
[SWS_Dcm_01586] [SWS_Dcm_01587]
[SWS_Dcm_91088]
[RS_Diag_04248] Support of session control [SWS_Dcm_00311]
service
[RS_Diag_04249] Support of session layer service [SWS_Dcm_00024] [SWS_Dcm_00027]
[SWS_Dcm_00111] [SWS_Dcm_00112]
[SWS_Dcm_00114] [SWS_Dcm_00115]
[SWS_Dcm_00117] [SWS_Dcm_00141]
[SWS_Dcm_00143] [SWS_Dcm_00557]
[SWS_Dcm_00654] [SWS_Dcm_00669]
[SWS_Dcm_00671] [SWS_Dcm_00673]
[SWS_Dcm_00703] [SWS_Dcm_00837]
[SWS_Dcm_00839] [SWS_Dcm_01073]
[SWS_Dcm_01145] [SWS_Dcm_01425]
[RS_Ids_00810] Basic SW security events [SWS_Dcm_01589] [SWS_Dcm_01590]
[SRS_BSW_00003] All software modules shall [SWS_Dcm_00065]
provide version and identification
information
[SRS_BSW_00005] Modules of the µC Abstraction [SWS_Dcm_NA_00999]
Layer (MCAL) may not have
hard coded horizontal interfaces
[SRS_BSW_00006] The source code of software [SWS_Dcm_NA_00999]
modules above the µC
Abstraction Layer (MCAL) shall
not be processor and compiler
dependent.
[SRS_BSW_00007] All Basic SW Modules written in [SWS_Dcm_NA_00999]
C language shall conform to the
MISRA C 2012 Standard.
[SRS_BSW_00009] All Basic SW Modules shall be [SWS_Dcm_NA_00999]
documented according to a
common standard.
[SRS_BSW_00010] The memory consumption of all [SWS_Dcm_NA_00999]
Basic SW Modules shall be
documented for a defined
configuration for all supported
platforms.
[SRS_BSW_00101] The Basic Software Module shall [SWS_Dcm_00033] [SWS_Dcm_00034]
be able to initialize variables and [SWS_Dcm_00035] [SWS_Dcm_00036]
hardware in a separate [SWS_Dcm_00037]
initialization function
[SRS_BSW_00158] No description [SWS_Dcm_NA_00999]
[SRS_BSW_00159] All modules of the AUTOSAR [SWS_Dcm_NA_00999]
Basic Software shall support a
tool based configuration
[SRS_BSW_00160] Configuration files of AUTOSAR [SWS_Dcm_NA_00999]
Basic SW module shall be
readable for human beings

37 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Requirement Description Satisfied by

[SRS_BSW_00161] The AUTOSAR Basic Software [SWS_Dcm_NA_00999]
shall provide a microcontroller
abstraction layer which provides
a standardized interface to
higher software layers
[SRS_BSW_00162] The AUTOSAR Basic Software [SWS_Dcm_NA_00999]
shall provide a hardware
abstraction layer
[SRS_BSW_00164] The Implementation of interrupt [SWS_Dcm_NA_00999]
service routines shall be done
by the Operating System,
complex drivers or modules
[SRS_BSW_00167] All AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Modules shall provide
configuration rules and
constraints to enable plausibility
checks
[SRS_BSW_00168] SW components shall be tested [SWS_Dcm_NA_00999]
by a function defined in a
common API in the Basis-SW
[SRS_BSW_00170] The AUTOSAR SW Components [SWS_Dcm_NA_00999]
shall provide information about
their dependency from faults,
signal qualities, driver demands
[SRS_BSW_00171] Optional functionality of a [SWS_Dcm_NA_00999]
Basic-SW component that is not
required in the ECU shall be
configurable at pre-compile-time
[SRS_BSW_00172] The scheduling strategy that is [SWS_Dcm_NA_00999]
built inside the Basic Software
Modules shall be compatible
with the strategy used in the
system
[SRS_BSW_00300] All AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Modules shall be identified by an
unambiguous name
[SRS_BSW_00301] All AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Modules shall only import the
necessary information
[SRS_BSW_00304] All AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Modules shall use the following
data types instead of native C
data types
[SRS_BSW_00305] Data types naming convention [SWS_Dcm_NA_00999]
[SRS_BSW_00306] AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Modules shall be compiler and
platform independent
[SRS_BSW_00307] Global variables naming [SWS_Dcm_NA_00999]
convention
[SRS_BSW_00308] AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Modules shall not define global
data in their header files, but in
the C file

38 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Requirement Description Satisfied by

[SRS_BSW_00309] All AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Modules shall indicate all global
data with read-only purposes by
explicitly assigning the const
keyword
[SRS_BSW_00310] API naming convention [SWS_Dcm_NA_00999]
[SRS_BSW_00312] Shared code shall be reentrant [SWS_Dcm_NA_00999]
[SRS_BSW_00314] All internal driver modules shall [SWS_Dcm_NA_00999]
separate the interrupt frame
definition from the service
routine
[SRS_BSW_00318] Each AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Module file shall provide version
numbers in the header file
[SRS_BSW_00321] The version numbers of [SWS_Dcm_NA_00999]
AUTOSAR Basic Software
Modules shall be enumerated
according specific rules
[SRS_BSW_00323] All AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Modules shall check passed API
parameters for validity
[SRS_BSW_00325] The runtime of interrupt service [SWS_Dcm_NA_00999]
routines and functions that are
running in interrupt context shall
be kept short
[SRS_BSW_00327] Error values naming convention [SWS_Dcm_NA_00999]
[SRS_BSW_00328] All AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Modules shall avoid the
duplication of code
[SRS_BSW_00330] It shall be allowed to use macros [SWS_Dcm_NA_00999]
instead of functions where
source code is used and runtime
is critical
[SRS_BSW_00331] All Basic Software Modules shall [SWS_Dcm_NA_00999]
strictly separate error and status
information
[SRS_BSW_00333] For each callback function it [SWS_Dcm_NA_00999]
shall be specified if it is called
from interrupt context or not
[SRS_BSW_00334] All Basic Software Modules shall [SWS_Dcm_NA_00999]
provide an XML file that contains
the meta data
[SRS_BSW_00335] Status values naming [SWS_Dcm_NA_00999]
convention
[SRS_BSW_00336] Basic SW module shall be able [SWS_Dcm_NA_00999]
to shutdown
[SRS_BSW_00337] Classification of development [SWS_Dcm_00040]
errors
[SRS_BSW_00339] Reporting of production relevant [SWS_Dcm_NA_00999]
error status
[SRS_BSW_00341] Module documentation shall [SWS_Dcm_NA_00999]
contains all needed informations

39 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Requirement Description Satisfied by

[SRS_BSW_00342] It shall be possible to create an [SWS_Dcm_NA_00999]
AUTOSAR ECU out of modules
provided as source code and
modules provided as object
code, even mixed
[SRS_BSW_00343] The unit of time for specification [SWS_Dcm_NA_00999]
and configuration of Basic SW
modules shall be preferably in
physical time unit
[SRS_BSW_00344] BSW Modules shall support [SWS_Dcm_NA_00999]
link-time configuration
[SRS_BSW_00345] BSW Modules shall support [SWS_Dcm_NA_00999]
pre-compile configuration
[SRS_BSW_00346] All AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Modules shall provide at least a
basic set of module files
[SRS_BSW_00347] A Naming seperation of different [SWS_Dcm_NA_00999]
instances of BSW drivers shall
be in place
[SRS_BSW_00350] All AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Modules shall allow the
enabling/disabling of detection
and reporting of development
errors.
[SRS_BSW_00351] Encapsulation of compiler [SWS_Dcm_NA_00999]
specific methods to map objects
[SRS_BSW_00353] All integer type definitions of [SWS_Dcm_NA_00999]
target and compiler specific
scope shall be placed and
organized in a single type
header
[SRS_BSW_00357] For success/failure of an API call [SWS_Dcm_NA_00999]
a standard return type shall be
defined
[SRS_BSW_00358] The return type of init() functions [SWS_Dcm_NA_00999]
implemented by AUTOSAR
Basic Software Modules shall be
void
[SRS_BSW_00359] All AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Modules callback functions shall
avoid return types other than
void if possible
[SRS_BSW_00360] AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Modules callback functions are
allowed to have parameters
[SRS_BSW_00361] All mappings of not standardized [SWS_Dcm_NA_00999]
keywords of compiler specific
scope shall be placed and
organized in a compiler specific
type and keyword header
[SRS_BSW_00369] All AUTOSAR Basic Software [SWS_Dcm_00044]
Modules shall not return specific
development error codes via the
API

40 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Requirement Description Satisfied by

[SRS_BSW_00371] The passing of function pointers [SWS_Dcm_NA_00999]
as API parameter is forbidden
for all AUTOSAR Basic Software
Modules
[SRS_BSW_00373] The main processing function of [SWS_Dcm_00053]
each AUTOSAR Basic Software
Module shall be named
according the defined
convention
[SRS_BSW_00374] All Basic Software Modules shall [SWS_Dcm_NA_00999]
provide a readable module
vendor identification
[SRS_BSW_00375] Basic Software Modules shall [SWS_Dcm_NA_00999]
report wake-up reasons
[SRS_BSW_00377] A Basic Software Module can [SWS_Dcm_NA_00999]
return a module specific types
[SRS_BSW_00378] AUTOSAR shall provide a [SWS_Dcm_NA_00999]
boolean type
[SRS_BSW_00379] All software modules shall [SWS_Dcm_NA_00999]
provide a module identifier in the
header file and in the module
XML description file.
[SRS_BSW_00380] Configuration parameters being [SWS_Dcm_NA_00999]
stored in memory shall be
placed into separate c-files
[SRS_BSW_00383] The Basic Software Module [SWS_Dcm_NA_00999]
specifications shall specify
which other configuration files
from other modules they use at
least in the description
[SRS_BSW_00384] The Basic Software Module [SWS_Dcm_NA_00999]
specifications shall specify at
least in the description which
other modules they require
[SRS_BSW_00385] List possible error notifications [SWS_Dcm_NA_00999]
[SRS_BSW_00386] The BSW shall specify the [SWS_Dcm_NA_00999]
configuration for detecting an
error
[SRS_BSW_00388] Containers shall be used to [SWS_Dcm_NA_00999]
group configuration parameters
that are defined for the same
object
[SRS_BSW_00389] Containers shall have names [SWS_Dcm_NA_00999]
[SRS_BSW_00390] Parameter content shall be [SWS_Dcm_NA_00999]
unique within the module
[SRS_BSW_00392] Parameters shall have a type [SWS_Dcm_NA_00999]
[SRS_BSW_00393] Parameters shall have a range [SWS_Dcm_NA_00999]
[SRS_BSW_00394] The Basic Software Module [SWS_Dcm_NA_00999]
specifications shall specify the
scope of the configuration
parameters

41 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Requirement Description Satisfied by

[SRS_BSW_00395] The Basic Software Module [SWS_Dcm_NA_00999]
specifications shall list all
configuration parameter
dependencies
[SRS_BSW_00396] The Basic Software Module [SWS_Dcm_NA_00999]
specifications shall specify the
supported configuration classes
for changing values and
multiplicities for each parameter/
container
[SRS_BSW_00397] The configuration parameters in [SWS_Dcm_NA_00999]
pre-compile time are fixed
before compilation starts
[SRS_BSW_00398] The link-time configuration is [SWS_Dcm_NA_00999]
achieved on object code basis in
the stage after compiling and
before linking
[SRS_BSW_00399] Parameter-sets shall be located [SWS_Dcm_NA_00999]
in a separate segment and shall
be loaded after the code
[SRS_BSW_00400] Parameter shall be selected [SWS_Dcm_NA_00999]
from multiple sets of parameters
after code has been loaded and
started
[SRS_BSW_00401] Documentation of multiple [SWS_Dcm_NA_00999]
instances of configuration
parameters shall be available
[SRS_BSW_00402] Each module shall provide [SWS_Dcm_NA_00999]
version information
[SRS_BSW_00403] The Basic Software Module [SWS_Dcm_NA_00999]
specifications shall specify for
each parameter/container
whether it supports different
values or multiplicity in different
configuration sets
[SRS_BSW_00404] BSW Modules shall support [SWS_Dcm_NA_00999]
post-build configuration
[SRS_BSW_00405] BSW Modules shall support [SWS_Dcm_NA_00999]
multiple configuration sets
[SRS_BSW_00406] A static status variable denoting [SWS_Dcm_NA_00999]
if a BSW module is initialized
shall be initialized with value 0
before any APIs of the BSW
module is called
[SRS_BSW_00407] Each BSW module shall provide [SWS_Dcm_00065]
a function to read out the version
information of a dedicated
module implementation
[SRS_BSW_00408] All AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Modules configuration
parameters shall be named
according to a specific naming
rule

42 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Requirement Description Satisfied by

[SRS_BSW_00409] All production code error ID [SWS_Dcm_NA_00999]
symbols are defined by the Dem
module and shall be retrieved by
the other BSW modules from
Dem configuration
[SRS_BSW_00410] Compiler switches shall have [SWS_Dcm_NA_00999]
defined values
[SRS_BSW_00411] All AUTOSAR Basic Software [SWS_Dcm_NA_00999]
Modules shall apply a naming
rule for enabling/disabling the
existence of the API
[SRS_BSW_00413] An index-based accessing of the [SWS_Dcm_NA_00999]
instances of BSW modules shall
be done
[SRS_BSW_00414] Init functions shall have a pointer [SWS_Dcm_NA_00999]
to a configuration structure as
single parameter
[SRS_BSW_00415] Interfaces which are provided [SWS_Dcm_NA_00999]
exclusively for one module shall
be separated into a dedicated
header file
[SRS_BSW_00416] The sequence of modules to be [SWS_Dcm_NA_00999]
initialized shall be configurable
[SRS_BSW_00417] Software which is not part of the [SWS_Dcm_NA_00999]
SW-C shall report error events
only after the DEM is fully
operational.
[SRS_BSW_00419] If a pre-compile time [SWS_Dcm_NA_00999]
configuration parameter is
implemented as "const" it should
be placed into a separate c-file
[SRS_BSW_00422] Pre-de-bouncing of error status [SWS_Dcm_NA_00999]
information is done within the
DEM
[SRS_BSW_00423] BSW modules with AUTOSAR [SWS_Dcm_NA_00999]
interfaces shall be describable
with the means of the SW-C
Template
[SRS_BSW_00424] BSW module main processing [SWS_Dcm_00053]
functions shall not be allowed to
enter a wait state
[SRS_BSW_00425] The BSW module description [SWS_Dcm_NA_00999]
template shall provide means to
model the defined trigger
conditions of schedulable
objects
[SRS_BSW_00426] BSW Modules shall ensure data [SWS_Dcm_NA_00999]
consistency of data which is
shared between BSW modules
[SRS_BSW_00427] ISR functions shall be defined [SWS_Dcm_NA_00999]
and documented in the BSW
module description template

43 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Requirement Description Satisfied by

[SRS_BSW_00428] A BSW module shall state if its [SWS_Dcm_NA_00999]
main processing function(s) has
to be executed in a specific
order or sequence
[SRS_BSW_00429] Access to OS is restricted [SWS_Dcm_NA_00999]
[SRS_BSW_00432] Modules should have separate [SWS_Dcm_NA_00999]
main processing functions for
read/receive and write/transmit
data path
[SRS_BSW_00433] Main processing functions are [SWS_Dcm_NA_00999]
only allowed to be called from
task bodies provided by the
BSW Scheduler
[SRS_BSW_00437] Memory mapping shall provide [SWS_Dcm_NA_00999]
the possibility to define RAM
segments which are not to be
initialized during startup
[SRS_BSW_00438] Configuration data shall be [SWS_Dcm_00037]
defined in a structure
[SRS_BSW_00439] Enable BSW modules to handle [SWS_Dcm_NA_00999]
interrupts
[SRS_BSW_00440] The callback function invocation [SWS_Dcm_NA_00999]
by the BSW module shall follow
the signature provided by RTE to
invoke servers via Rte_Call API
[SRS_BSW_00441] Naming convention for type, [SWS_Dcm_NA_00999]
macro and function
[SRS_BSW_00447] Standardizing Include file [SWS_Dcm_NA_00999]
structure of BSW Modules
Implementing Autosar Service
[SRS_BSW_00448] Module SWS shall not contain [SWS_Dcm_NA_00999]
requirements from Other
Modules
[SRS_BSW_00449] BSW Service APIs used by [SWS_Dcm_NA_00999]
Autosar Application Software
shall return a Std_ReturnType
[SRS_BSW_00450] A Main function of a [SWS_Dcm_NA_00999]
un-initialized module shall return
immediately
[SRS_BSW_00451] Hardware registers shall be [SWS_Dcm_NA_00999]
protected if concurrent access to
these registers occur
[SRS_BSW_00452] Classification of runtime errors [SWS_Dcm_01416]
[SWS_Dcm_NA_00999]
[SRS_BSW_00453] BSW Modules shall be [SWS_Dcm_NA_00999]
harmonized
[SRS_BSW_00454] An alternative interface without a [SWS_Dcm_NA_00999]
parameter of category DATA_
REFERENCE shall be available.
[SRS_BSW_00456] A Header file shall be defined in [SWS_Dcm_NA_00999]
order to harmonize BSW
Modules

44 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Requirement Description Satisfied by

[SRS_BSW_00457] Callback functions of Application [SWS_Dcm_NA_00999]
software components shall be
invoked by the Basis SW
[SRS_BSW_00458] Classification of production [SWS_Dcm_NA_00999]
errors
[SRS_BSW_00459] It shall be possible to [SWS_Dcm_NA_00999]
concurrently execute a service
offered by a BSW module in
different partitions
[SRS_BSW_00460] Reentrancy Levels [SWS_Dcm_NA_00999]
[SRS_BSW_00461] Modules called by generic [SWS_Dcm_NA_00999]
modules shall satisfy all
interfaces requested by the
generic module
[SRS_BSW_00462] All Standardized Autosar [SWS_Dcm_NA_00999]
Interfaces shall have unique
requirement Id / number
[SRS_BSW_00463] Naming convention of callout [SWS_Dcm_NA_00999]
prototypes
[SRS_BSW_00464] File names shall be considered [SWS_Dcm_NA_00999]
case sensitive regardless of the
filesystem in which they are
used
[SRS_BSW_00465] It shall not be allowed to name [SWS_Dcm_NA_00999]
any two files so that they only
differ by the cases of their letters
[SRS_BSW_00466] Classification of extended [SWS_Dcm_NA_00999]
production errors
[SRS_BSW_00467] The init / deinit services shall [SWS_Dcm_NA_00999]
only be called by BswM or EcuM
[SRS_BSW_00469] Fault detection and healing of [SWS_Dcm_NA_00999]
production errors and extended
production errors
[SRS_BSW_00470] Execution frequency of [SWS_Dcm_NA_00999]
production error detection
[SRS_BSW_00471] Do not cause dead-locks on [SWS_Dcm_NA_00999]
detection of production errors -
the ability to heal from previously
detected production errors
[SRS_BSW_00472] Avoid detection of two [SWS_Dcm_NA_00999]
production errors with the same
root cause.
[SRS_BSW_00473] Classification of transient faults [SWS_Dcm_NA_00999]
[SRS_BSW_00477] The functional interfaces of [SWS_Dcm_NA_00999]
AUTOSAR BSW modules shall
be specified in C90
[SRS_BSW_00478] Timing limits of main functions [SWS_Dcm_NA_00999]
[SRS_BSW_00479] Interfaces for handling request [SWS_Dcm_NA_00999]
from external devices
[SRS_BSW_00480] NullPointer Errors shall follow a [SWS_Dcm_NA_00999]
naming rule
[SRS_BSW_00481] Invalid configuration set [SWS_Dcm_NA_00999]
selection errors shall follow a
naming rule

45 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Requirement Description Satisfied by

[SRS_BSW_00482] Get Version Informationfunction [SWS_Dcm_00065]
shall follow a naming rule

7 Functional specification

7.1 Security Events

[SWS_Dcm_01589] dIf security event reporting has been enabled for the Dcm module
( DcmEnableSecurityEventReporting = true) the respective security events shall
be reported to the IdsM via the interfaces defined in AUTOSAR_SWS_BSWGeneral.c
(RS_Ids_00810)
[SWS_Dcm_01590] Security events for DCM dThe following table lists the security
events which are standardized for the Dcm together with their trigger conditions.
Context data is not provided by the Dcm for the security events.c(RS_Ids_00810)
Name Description ID
DIAG_SEV_WRITE_INVALID_DATA Tester writes invalid data with service WriteDataBy 23
Identifier.
DIAG_SEV_SECURITY_ACCESS_DENIED Tester has send an diagnostic request without meeting the 24
servers security level requirements for that service. NRC
0x33 (securityAccessDenied) was returned.
DIAG_SEV_COMMUNICATION_CONTROL_ ECU communicationwas switched off with service 25
SWITCHED_OFF CommunicationControl.
DIAG_SEV_SERVICE_NOT_SUPPORTED A diagnostic service war requested that is not supported or 26
not supported in the active session. NRC 0x11 (serviceNot
Supported) or NRC 0x7F (serviceNotSupportedInActive
Session) was returned.
DIAG_SEV_SUBFUNCTION_NOT_ A subfunction of a diagnostic service was requested that is 27
SUPPORTED not supported for the requested service.
DIAG_SEV_INCORRECT_MESSAGE_ Received request message does not match the specified 28
LENGTH_OR_FORMAT length or the format of the parameters is different from the
specified ones for that service. NRC 0x13 (incorrect
MessageLengthOrInvalidFormat) was returned.
DIAG_SEV_REQUEST_SEQUENCE_ERROR A diagnostic service was received in the wrong sequence 29
order. NRC 0x24 (requestSequenceError) was returned.
DIAG_SEV_REQUEST_OUT_OF_RANGE A diagnsotic request with a parameter that is our range of 30
the allowed bounds wa received. A NRC 0x31 (requestOut
OfRange) was returned.
DIAG_SEV_REQUESTED_ACTIONS_ A diagnostic request was received while the required 31
REQUIRES_AUTHENTICATION authentication to executie this service is not given. NRC
0x34 (authenticationRequired) was returned.
DIAG_SEV_SECURITY_ACCESS_NUMBER_ Security Access failed and the number of invalid attempts 32
OF_ATTEMPTS_EXCEEDED has been exceeded. NRC 0x36 (exceedNumberOf
Attempts) was returned.
DIAG_SEV_SECURITY_ACCESS_INVALID_ Security Access failed because the tester has send an 33
KEY invalid key to the server. An NRC 0x35 (invalidKey) was
returned.
5

46 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Name Description ID
DIAG_SEV_SECURITY_ACCESS_REQUIRED_ A further attempt to unlock the ECU was taken before the 34
TIME_DELAY_NOT_EXPIRED delay time had expired. NRC 0x37 (requiredTimeDelayNot
Expired) was sent.
DIAG_SEV_NUMBER_OF_FAILED_ Number of failed authentification attempts - OEM specific 35
AUTHENTICATION_ATTEMPTS_EXCEEDED
DIAG_SEV_CERTIFICATE_FAILURE The tester tried an authentication with an invalid certficate. 36
DIAG_SEV_ECU_UNLOCK_SUCCESSFUL Successful unlocked the ECU (via Security Access $27), 37
per Level
DIAG_SEV_AUTHENTICATION_SUCCESSFUL Succesfully authenticated (via Authentication $29) 38
DIAG_SEV_CLEAR_DTC_SUCCESSFUL DTC information has been cleared by SID 0x14 Clear 39
DTCInformation
DIAG_SEV_ECU_RESET ECU had been reset by SID 0x11 ResetECU 40
DIAG_SEV_WRITE_DATA Diagnostic data identifier have been written by SID 0x2E. 41
DIAG_SEV_REQUEST_DOWNLOAD A diagnsotic data download sequence was requested with 42
SID 0x34.
DIAG_SEV_DTC_SETTING_SWITCHED_OFF DTC setting switched off with service 0x85 (Control 43
DTCSetting).

7.2 Error Classification

This section describes how the Dcm module has to treat the several error classes that
may happen during the life cycle of the Dcm module.
Diagnostic-Communication-Errors are handled directly in the ISO-Protocols by NRCs.
[SWS_Dcm_00044] dThe error values shall be the unique for all error types. The Dcm
shall use only the values given in this chapter.c(SRS_BSW_00369)
Section ”Error Handling” of the document ”General Specification of Basic Software
Modules” describes the error handling of the Basic Software in detail. Above all, it
constitutes a classification scheme consisting of five error types which may occur in
BSW modules.
Based on this foundation, the following section specifies particular errors arranged in
the respective subsections below.

7.2.1 Development Errors

The errors and exceptions described in [SWS_Dcm_00040] shall be detectable by the

Dcm module depending on its build version (development/production mode).
[SWS_Dcm_00040] d

47 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Type of error Related error code Error value

Interface return-value is out of range DCM_E_INTERFACE_RETURN_VALUE 0x02
The Dcm is getting called with an invalid input DCM_E_INVALID_VALUE 0x02
parameter value or the Dcm has called an function
and this function returns an invalid out parameter
or return value.
Internal:Dcm not initialized DCM_E_UNINIT 0x05
Dcm API function with invalid input parameter DCM_E_PARAM 0x06
Dcm API service invoked with NULL POINTER as DCM_E_PARAM_POINTER 0x07
parameter
Dcm initialisation failed DCM_E_INIT_FAILED 0x08
Storing the ProgConditions failed DCM_E_SET_PROG_CONDITIONS_FAIL 0x09

c(SRS_BSW_00337)

7.2.2 Runtime Errors

The errors and exceptions described in [SWS_Dcm_01416] shall be detectable by the

Dcm module depending on its build version (development/production mode).
[SWS_Dcm_01416] d
Type of error Related error code Error value
Interface: Timeout occurred during interaction with DCM_E_INTERFACE_TIMEOUT 0x01
another module (e.g. maximum number of
response pending is reached, refer to
[SWS_Dcm_00120])
Interface: Boundary check of buffers provided by DCM_E_INTERFACE_BUFFER_OVERFLOW 0x03
the Dcm failed during interaction with another
module (application, Dem,PduR, etc.)

c(SRS_BSW_00452)

7.2.3 Transient Faults

There are no transient faults.

7.2.4 Production Errors

There are no production errors.

7.2.5 Extended Production Errors

There are no extended production errors.

48 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.3 General design elements

7.3.1 Submodules within the Dcm module

To define the functionality of the Dcm module, The Dcm SWS models the Dcm module
as consisting of the following submodules:
• Diagnostic Session Layer (DSL) submodule: The DSL submodule ensures data
flow concerning diagnostic requests and responses, supervises and guarantees
diagnostic protocol timing and manages diagnostic states (especially diagnostic
session and security).
• Diagnostic Service Dispatcher (DSD) submodule: The DSD submodule pro-
cesses a stream of diagnostic data. The submodule:
– Receives a new diagnostic request over a network and forwards it to a data
processor.
– Transmits a diagnostic response over a network when triggered by the data
processor (e.g. by the DSP submodule).
• Diagnostic Service Processing (DSP) submodule: The DSP submodule handles
the actual diagnostic service (respectively subservice) requests.
The next graphic gives an overview of the interfaces between the submodules DSP,
DSD, and DSL within the Dcm module.

DspInternal_CancelPagedBufferProcessing()
DEM Interface DEM
Xxx_ReadData() DsdInternal_ProcessPage()
Xxx_WriteData()
Xxx_ReadDataLength() DspInternal_DcmUpdatePage()
DsdInternal_StartPagedProcessing()
Xxx_ConditionCheckRead()
Xxx_GetScalingInformation()
DSD
Service Interpreter calls
Xxx_ReturnControlToECU()
Xxx_ResetToDefault() DspInternal_DcmConfirmation()
Xxx_FreezeCurrentState() DSP
Xxx_ShortTermAdjustment() <Module>_<DiagnosticService>_<SubService>
RTE (Application)

() <Module>_<DiagnosticService>()
Xxx_GetInfoTypeValue()
Xxx_IsDidAvailable()
Xxx_WriteDidData()
Data Confirmation functionality
Data Indication functionality

Xxx_ReadDidData()
Xxx_Start()
Transmit functionality

Xxx_Stop()
Xxx_RequestResults()
Xxx_RequestControl()
External
Xxx_GetSeed()
Xxx_CompareKey() module
Xxx_Indication()
Xxx_Confirmation() PDU Router
Dcm_StartOfReception()
Dcm_CopyRxData()
DslInternal_SetSesCtrlType() Dcm_CopyTxData()
Dcm_TpRxIndication()
DslInternal_SetSecurityLevel()
Dcm_TpTxConfirmation()
PduR_DcmTransmit()
PduR_DcmCancelTransmit()
DSL PduR_DcmCancelReceive()
Dcm_ResetToDefaultSession()
Dcm_GetSecurityLevel( COM Manager
Dcm_GetSesCtrlTypel( *1 | see page
Dcm_GetActiveProtocol()
Xxx_StartProtocol() *2 | before
|
Xxx_StopProtocol() Dcm_Init() |

Figure 7.1: Possible interaction between the submodules in the DCM

49 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Note: The implementation of these submodules and the interfaces between them is
not mandatory. They are introduced only to improve the readability of the specification.

7.3.2 Negative Response Code (NRC)

The standards defining the UDS Services and OBD Services define the negative re-
sponse codes (NRCs). The Dcm SWS uses these NRCs in the interfaces between the
Dcm and other BSW modules and the SW-Cs. These NRCs are defined in the data
type Dcm_NegativeResponseCodeType.
[SWS_Dcm_01075] dThe order of the transmitted NRC shall be compliant with the one
described in ISO14229-1 [1].c()

7.3.3 Non-volatile information

Several features of the Dcm require non-volatile information to be initialized. AUTOSAR

does not describe how this information is accessed or if the information is already avail-
able when the Dcm is initialized. Therefore the access for the non-volatile information
is implementation specific and has to be ensured during integration.
[SWS_Dcm_00870] dThe Dcm shall check if the NvM is read out correctly. If the non-
volatile information could not read out correct the Dcm shall start a default reaction.
The default reaction is described in the chapter were the usage of the non-volatile data
is described.c()
[SWS_Dcm_01048] dIf the Dcm cancels a service with NvM access, it shall call
NvM_CancelJobs().c()
The service is cancelled either by reaching the maximum number of RCRRP NRCs or
by protocol preemption.

7.3.4 Types

[SWS_Dcm_00969] dThe Dcm shall treat non-integer data types (e.g. uint8[n]) either
like integer data types of the matching size or leave their contents uninterpreted in case
DcmDspDataEndianness is configured to OPAQUE.c()
[SWS_Dcm_00970] dThe Dcm module shall interpret opaque data as uint8[n] and shall
always map it to an n-bytes sized signal. For opaque data endianness, DcmDsp-
DataEndianness has to be configured to OPAQUE.c()
[SWS_Dcm_00971] dThe Dcm shall extend the endianness conversion defined in [9],
to signed data types.c()
In [9] (Chapter 2.4) the endianness conversion is defined for unsigned data types. The
associated configurations can be found in the configuration ?? DcmDspData.

50 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.3.4.1 Atomic types overview

Figure 7.2: Atomic types overview

7.3.4.2 Data array types overview

Figure 7.3: Data array types overview

7.3.4.3 Data types constraints

[SWS_Dcm_CONSTR_6002] Existence of size parameter dDcmDspDataByte-

Size shall be present if DcmDspDataType is set to: UINT8_N, SINT8_N, UINT16_N,
SINT16_N, UINT32_N, SINT32_N or UINT8_DYN.c()
Note: DcmDspDataByteSize is not required for primitive datatypes
[SWS_Dcm_CONSTR_6035] Restrictions on size parameter for 16 Bit arrays d
DcmDspDataByteSize shall be a multiple of 2 if the value is greater than 2 and
DcmDspDataType is UINT16_N or SINT16_N.c()
[SWS_Dcm_CONSTR_6036] Restrictions on size parameter for 32 Bit arrays d
DcmDspDataByteSize shall be a multiple of 4 if the value is greater than 4 and
DcmDspDataType is UINT32_N or SINT32_N.c()
[SWS_Dcm_CONSTR_6008] Define the usage of DcmDspRoutineParameter-
Size parameter dDcmDspRoutineParameterSize is only required if DcmDspRou-
tineSignalType is set to SINT8_N, SINT16_N, SINT32_N, UINT8_N, UINT16_N,
UINT32_N or VARIABLE_LENGTH.c()
[SWS_Dcm_CONSTR_6011] Only last parameters in RID may have a variable
length dDcmDspRoutineSignalType with VARIABLE_LENGTH is only valid for the last
signal.c()
[SWS_Dcm_CONSTR_6012] Existence of size parameter dDcmDspPidDataByte-
Size shall be present if DcmDspPidDataType is set to: UINT8_N, SINT8_N,
UINT16_N, SINT16_N, UINT32_N or SINT32_N.c()

51 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Note: DcmDspPidDataByteSize is not required for primitive datatypes

[SWS_Dcm_CONSTR_6040] Restrictions on size parameter for 16 Bit arrays d
DcmDspPidDataByteSize shall be a multiple of 2 if the value is greater than 2 and
DcmDspPIDDataType is UINT16_N or SINT16_N.c()
[SWS_Dcm_CONSTR_6041] Restrictions on size parameter for 32 Bit arrays d
DcmDspPidDataByteSize shall be a multiple of 4 if the value is greater than 4 and
DcmDspPIDDataType is UINT32_N or SINT32_N.c()
UINT8 shall be used as (implementation) data type for bit lengths between 1 and 8
[SWS_Dcm_CONSTR_6038] Restrictions on datatype usage dDcmDspDataType
shall be UINT8_N, in case DcmDspDataUsePort is equal to USE_BLOCK_ID.c()
[SWS_Dcm_CONSTR_6026] Usage of variable data length in case of S/R com-
munication, NvRam access or ECU signal access dIn case DcmDspDataUse-
Port is set to {USE_DATA_SENDER_RECEIVER, USE_DATA_SENDER_RECEIVER_-
AS_SERVICE, USE_BLOCK_ID, USE_ECU_SIGNAL}, the usage of variable data length
shall be not allowed.c()
[SWS_Dcm_CONSTR_6031] dThe DcmDspData.SHORT-NAME and DcmDspPid-
Data.SHORT-NAME shall be distinct.c()
Note: Variable data length is only possible with UINT8 arrays with DcmDspDataType
set to UINT8_DYN.

7.3.4.4 Dcm_OpStatusType

For the operation using the Dcm_OpStatusType, the Dcm shall work as follow :
[SWS_Dcm_00527] dAt first call of an operation using the Dcm_OpStatusType, the
Dcm call the operation with OpStatus = DCM_INITIALc()
[SWS_Dcm_00528] dIf the value DCM_E_FORCE_RCRRP is returned from an oper-
ation using Dcm_OpStatusType, the Dcm shall invoke the transmit request for RCR-RP
(NRC 0x78 transmission) and the Dcm shall not realize further invocation of the opera-
tion till RCR-RP is transmitted.c()
[SWS_Dcm_00529] dAfter transmit confirmation of a RCR-RP transmitted on the con-
text of [SWS_Dcm_00528], the Dcm calls, from Dcm_MainFunction (due to call con-
text), the operation again with OpStatus = DCM_FORCE_RCRRP_OK.c()
[SWS_Dcm_00530] dIf a DCM_E_PENDING value is returned from an operation using
the Dcm_OpStatusType, the Dcm call the operation on each Dcm_MainFunction call
with OpStatus = DCM_PENDING as long as DCM_E_PENDING is returned.c()

52 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.3.4.5 Dcm_Cemr_{DID}Type

For ease of use in SWC, the Dcm generates a symbolic name to access the CEMR bit
according to Dcm_Cemr_{DID}Type (see [SWS_Dcm_91087]) for each data element
used in a DID with IO control. The SWC can work only with the generated symbolic
value of the bitfield text table to mask out a certain bit. This helps to avoid confusion,
while the first RID bit on the network controls the first parameter of the DID but that Bit
is the most significant Bit in the MSB. The symbolic name also helps if the size of the
RID is changing. In that case the bitmask changes as well, but the symbolic value is
always updated.

7.4 Diagnostic Session Layer (DSL)

7.4.1 Introduction

[SWS_Dcm_00030] dAll functional areas of the DSL submodule shall be in confor-

mance with the specifications ISO14229-1 [1], ISO14229-2 [10] and the network-
independent part of ISO15765-3 [4].c(RS_Diag_04003, RS_Diag_04015)
There is no network-dependent functional area in the DSL submodule. Within the con-
figuration, some parameters can be set dependent on the network.

7.4.2 Use cases

The DSL submodule provides the following functionalities:

• Session handling (as required by ISO14229-1 [1] and ISO 15765-3 [4])
• Application layer timing handling (as required by ISO14229-1 [1] and ISO 15765-
3 [4])
• Specific response behavior (as required by ISO14229-1 [1] and ISO 15765-3 [4])
• Authentication state handling per diagnostic connection (as required by ISO
14229-1:2018)
– Provide authentication state per connection
– Manage authentication state transitions

7.4.3 Interaction with other modules

The DSL has the following interaction with other modules:

• PduR module

53 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

– PduR module provides data of incoming diagnostic requests.

– The DSL submodule triggers output of diagnostic responses.
• DSD submodule
– The DSL submodule informs the DSD submodule about incoming requests
and provides the data.
– The DSD submodule triggers output of diagnostic responses.
• SW-Cs / DSP submodule. The DSL submodule provides access to security and
session state.
• ComM module
– The DSL submodule guarantees the communication behavior required by
the ComM module

7.4.4 Functional description

7.4.4.1 Overview

The DSL submodule provides the following functionality:

Request Handling
• Forward requests from the PduR module to the DSD submodule.
• Concurrent TesterPresent (”keep alive logic”).
Response Handling
• Forward responses from the DSD submodule to the PduR module.
• Guarantee response timing to tester.
• Support of periodic transmission.
• Support of ResponseOnEvent (ROE) transmission.
• Support of segmented response.
• Support of ResponsePending response triggered by the application.
Security Level Handling
• Manage security level.
Session State Handling
• Manage session state.
• Keep track of active non-default sessions.

54 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• Allows modifying timings.

Diagnostic Protocol Handling
• Handling of different diagnostic protocols.
• Manage resources.
Communication Mode Handling
• Handling of communication requirements (Full- / Silent- / No Communication).
• Indicating of active / inactive diagnostic.
• Enabling / disabling all kinds of diagnostic transmissions.

7.4.4.2 Forward requests from the PduR module to the DSD submodule

The PduR module indicates the Dcm module whenever a reception of new diagnostic
request content is started on a DcmDslProtocolRxPduId, which is assigned to the
Dcm module. This is done by calling Dcm_StartOfReception, which inform the Dcm
module of the data size to be received and provides the data of the first frame or single
frame, and allows the Dcm to reject the reception if the data size overflows its buffer
size, or if the requested service is not available. The further call to Dcm_CopyRxData
request the Dcm module to copy the data from the provided buffer to the Dcm buffer.
If the reception of a diagnostic request is finished (when Dcm_StartOfReception
succeeded) the PduR module will call Dcm_TpRxIndication to give a receive indi-
cation to the Dcm module. The Dcm shall be able to use generic connections, where
the addressing information is provided to Dcm by Dcm_StartOfReception via the
MetaData of the DcmRxPdu. This addressing information must be stored and used for
the response and for detection of requests from the same tester. see section 7.4.4.5
Generic Connection Handling for further details.
[SWS_Dcm_00111] dThe DSL submodule shall forward received data to the DSD sub-
module only after a call of Dcm_TpRxIndication with parameter Result = E_OK (see
[SWS_Dcm_00093]).c(RS_Diag_04249)
[SWS_Dcm_00241] dAs soon as a request message is received (after a call of Dcm_-
TpRxIndication with parameter Result = E_OK (see [SWS_Dcm_00093]) and until
a call to Dcm_TpTxConfirmation (see [SWS_Dcm_00351]) for the associated Tx-
DcmPduId), the DSL submodule shall block the corresponding DcmPduId. During the
processing of this request, no other request of the same DcmDslConnection (e.g.
an enhanced session can be ended by a OBD session) can be received, until the corre-
sponding response message is sent and the DcmPduId is released again (except for
Concurrent TesterPresent requests).c()
More descriptions of the APIs (prototype, input/output parameter) can be found in the
interface description of PduR module [11].

55 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

It is allowed to have different DcmPduIds for different diagnostic communication appli-

cations. For example:
• OBD DcmDslProtocolRxPduId: for reception of OBD requests,
• OBD DcmTxPduId: for transmission of OBD responses,
• UDS phys DcmDslProtocolRxPduId: for reception of UDS physically addressed
requests,
• UDS func DcmDslProtocolRxPduId: for reception of UDS functionally ad-
dressed requests,
• UDS DcmTxPduId: for transmission of UDS responses.
Address type (physical/functional addressing) is configured per DcmDslProtocol-
RxPduId. A configuration per DcmDslProtocolRxPduId is possible because there
will always be different DcmDslProtocolRxPduId values for functional and physi-
cal receptions, independent of the addressing format of the Transport Layer (extended
addressing, normal addressing).

7.4.4.2.1 Dcm_StartOfReception

[SWS_Dcm_00444] dIf the requested size is large than the buffer available in the
DCM, the function Dcm_StartOfReception shall return BUFREQ_E_OVFL (see
[SWS_Dcm_00094]).c()
[SWS_Dcm_00788] dWhen processing a diagnostic request and in case DcmDslDia-
gRespOnSecondDeclinedRequest is set to TRUE, the Dcm module shall return
BUFREQ_OK on Dcm_StartOfReception received on new request using a different
DcmDslConnection.c()
[SWS_Dcm_00789] dIn case [SWS_Dcm_00788], the Dcm respond with a NRC 0x21c
()
[SWS_Dcm_00790] dWhen processing a diagnostic request, the Dcm module shall
reject (Dcm_StartOfReception shall return BUFREQ_E_NOT_OK) any new re-
quest using a different DcmDslConnection in case DcmDslDiagRespOnSecond-
DeclinedRequest is set to FALSE until the current diagnostic request processing is
over.c()
[SWS_Dcm_00557] dWhen processing a diagnostic request, the Dcm module shall
reject (Dcm_StartOfReception shall return BUFREQ_E_NOT_OK) any new diag-
nostic request with the same DcmDslConnection until the current diagnostic request
processing is over. Concurrent TesterPresent requests will be accepted with a
BUFREQ_OK, but not further processed, as the running diagnostic request already
resets the session timeout timer (S3Server).c(RS_Diag_04249)
[SWS_Dcm_01145] dIf the current session is a non-default session and a Concur-
rent TesterPresent received on a different DcmDslConnection, this request will

56 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

be accepted with a BUFREQ_OK, but not further processed. E.g. it is not resetting the
session timeout timer (S3Server)c(RS_Diag_04249)
[SWS_Dcm_01146] dIn case of [SWS_Dcm_01145] with reception on a higher priority
protocol, this will not lead to protocol preemption.c()
[SWS_Dcm_00642] dWhen the API Dcm_StartOfReception is invoked with TpSd-
uLength equal to 0, the value BUFREQ_E_NOT_OK shall be returned and no further
action shall be taken.c(RS_Diag_04147)
[SWS_Dcm_00655] dIf the current session is a non-default session and a new
diagnostic request with same or lower priority protocol than active one is de-
tected, the Dcm shall act according [SWS_Dcm_00788], [SWS_Dcm_00789] and
[SWS_Dcm_00790].c()
[SWS_Dcm_00656] dIf the current session is the default session and a diagnostic re-
quest is in execution, for any new diagnostic request with same or lower priority protocol
than active one, the Dcm shall act according [SWS_Dcm_00788], [SWS_Dcm_00789]
and [SWS_Dcm_00790].c()

7.4.4.2.2 Dcm_CopyRxData

[SWS_Dcm_00443] dIf Dcm_StartOfReception returns BUFREQ_OK, the further

call to Dcm_CopyRxData shall copy the data from the buffer provided in info parame-
ter) to the Dcm buffer and update the bufferSizePtr parameter with remaining free place
in Dcm receive buffer after completion of this call.c()
[SWS_Dcm_00996] dWhen the API Dcm_CopyRxData is invoked with SduLength
from info equal to 0, the value BUFREQ_OK shall be returned and bufferSizePtr shall
be filled with the remaining size of the Rx buffer.c()
Note: The size of the Rx buffer is based on the buffer length, which is returned in the
parameter RxBufferSizePtr of API Dcm_StartOfReception. [SWS_Dcm_00342]
dAfter starting to copy the received data (see [SWS_Dcm_00443]), the Dcm module
shall not access the receive buffer until it is notified by the service Dcm_TpRxIndica-
tion about the successful completion or unsuccessful termination of the reception.c
()
Note: Dcm_TpRxIndication is only expected when Dcm_StartOfReception suc-
ceeded

7.4.4.2.3 Dcm_TpRxIndication

[SWS_Dcm_00344] dIf Dcm_TpRxIndication is called with parameter Result dif-

ferent from E_OK, then the Dcm module shall not evaluate the buffer assigned to the
I-PDU, which is referenced in parameter DcmRxPduId.c()

57 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Rationale for [SWS_Dcm_00344]: It is undefined which part of the buffer contains valid
data in this case

7.4.4.3 Concurrent TesterPresent (”keep alive logic”)

It is possible, that functional ”TesterPresent” commands are sent by the tester in par-
allel to physical requests/responses. This is called ”keep alive logic” in ISO14229-1
[1]. This functional ”TesterPresent” will be received on a separate DcmDslProto-
colRxPduId belonging to a DcmDslProtocolRxPduId RxConnection which has
DcmDslProtocolRxAddrType configured as DCM_FUNCTIONAL_TYPE, which is
belonging to the same DcmDslConnection as the physical request. A Dcm-internal
receive buffer which is not configured explicitly, is used in this case. Due to that rea-
son, the functional TesterPresent (and only functional TesterPresent without response)
is handled in the following way:
[SWS_Dcm_00112] dWhen the PduR module calls Dcm_TpRxIndication with pa-
rameter Result=E_OK (see [SWS_Dcm_00093]) and if the request is a ”TesterPresent”
command with ”suppressPosRspMsgIndicationBit” set to TRUE (SID equal to 0x3E,
subfunction equal to 0x80), the DSL submodule shall reset the session timeout timer
(S3Server).c(RS_Diag_04249)
[SWS_Dcm_00113] dWhen the PduR module calls Dcm_TpRxIndication with pa-
rameter Result = E_OK (see [SWS_Dcm_00093]) and if the request is a ”TesterP-
resent” command with ”suppressPosRspMsgIndicationBit” set to TRUE (SID equal to
0x3E, subfunction equal to 0x80), the DSL submodule shall not forward this request to
the DSD submodule for further interpretation.c()
Rationale for [SWS_Dcm_00113]: Because of bypassing the functional ”TesterPre-
sent” in the DSL submodule, the Dcm module is able to receive and process next phys-
ical requests without any delay.
[SWS_Dcm_01168] dThe Dcm shall handle a tester present request as concurrent
request only if it was received on a functional address with ”suppressPosRspMsgIndi-
cationBit” set to TRUE.c()

7.4.4.3.1 Dcm_CopyTxData

If the copied data is smaller than the length requested to transmit within the service
PduR_DcmTransmit() the Dcm module will be requested by the service Dcm_CopyTx-
Data to provide another data when the current copied data have been transmitted.
[SWS_Dcm_00346] dIf the function Dcm_CopyTxData is called and the Dcm module
successfully copied the data in the buffer provided in info parameter, then the function
shall return BUFREQ_OK.c()
[SWS_Dcm_00350] dCaveats of Dcm_CopyTxData:

58 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• The value of parameter availableDataPtr of function Dcm_CopyTxData shall not

exceed the number of Bytes still to be sent.
• If this service returns BUFREQ_E_NOT_OK the transmit requests issued by
calling the service PduR_DcmTransmit() is still not finished. A final confirma-
tion (indicating an error with call of service Dcm_TpTxConfirmation) is re-
quired to finish this service and to be able to start another transmission (call
to PduR_DcmTransmit()). So it is up to the transport protocol to confirm the abort
of transmission.
c()

7.4.4.3.2 Dcm_TpTxConfirmation

[SWS_Dcm_00352] dIf the function Dcm_TpTxConfirmation is called, then the Dcm

module shall unlock the transmit buffer.c()
[SWS_Dcm_00353] dIf the function Dcm_TpTxConfirmation is called, then the Dcm
module shall stop error handling (Page buffer timeout, P2ServerMax/P2*ServerMax
timeout ).c()
For transmission via FlexRay the following restriction has to be considered: Since the
FlexRay Specification does not mandate the existence of a transmit interrupt, the exact
meaning of this confirmation (i.e. "transfer into the FlexRay controller’s send buffer" OR
"transmission onto the FlexRay network") depends on the capabilities of the FlexRay
communication controller and the configuration of the FlexRay Interface.

7.4.4.4 Forward responses from the DSD submodule to the PduR module

[SWS_Dcm_00114] dThe DSD submodule shall request the DSL submodule for trans-
mission of responses.c(RS_Diag_04249)
[SWS_Dcm_00115] dWhen the diagnostic response of a DcmDslMainConnection
is ready, the DSL submodule shall trigger the transmission of the diagnostic response
to the PduR module by calling PduR_DcmTransmit() using the corresponding DcmD-
slProtocolTxPduRef parameter as PduId.c(RS_Diag_04249)
[SWS_Dcm_01072] dIn case of PeriodicTransmission, the Dcm shall provide in the
call to PduR_DcmTransmit() the full payload data and expect no call to Dcm_CopyTx-
Data.c()
[SWS_Dcm_01073] dIn case of PeriodicTransmission, the Dcm will be called for pe-
riodic transmission with Dcm_TxConfirmation to indicate the transmission result.c
(RS_Diag_04249)
Responses are sent with the DcmTxPduId, which is linked in the Dcm module configura-
tion to the DcmDslProtocolRxPduId, i.e. the ID the request was received with (see

59 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

configuration parameter DcmDslProtocolTx) Within PduR_DcmTransmit() only the

length information and, for generic connections, the addressing information, is given to
the PduR module. After the Dcm module has called successfully PduR_DcmTransmit(),
the PduR module will call Dcm_CopyTxData to request the Dcm module to provide the
data to be transmitted and will call Dcm_TpTxConfirmation after the complete PDU
has successfully been transmitted or an error occurred. see section 7.4.4.5 "Generic
Connection Handling for further details on address information handling within generic
connections".
[SWS_Dcm_00117] dIf the DSL submodule receives a confirmation after the complete
Dcm PDU has successfully been transmitted or an error occurred by a call of Dcm_-
TpTxConfirmation, then the DSL submodule shall forward this confirmation to the
DSD submodule.c(RS_Diag_04249)
[SWS_Dcm_00118] dIn case of a failed transmission (failed PduR_DcmTransmit() re-
quest) or error confirmation (Dcm_TpTxConfirmation with error), the DSD submod-
ule shall not repeat the diagnostic response transmission.c()
Note: Dcm_TpTxConfirmation is only expected when PduR_DcmTransmit suc-
ceeded.
[SWS_Dcm_01166] dIf the Multiplicity of DcmDslProtocolTx is set to "0" the Dcm
shall process the received diagnostic request without sending a response.c()
More descriptions of the APIs (prototype, input/output parameter) can be found in the
interface description of the PduR module [11].

7.4.4.5 Generic Connection Handling

The Dcm shall be able to handle generic connections, identified by DcmPdus with Meta-
DataItems of type SOURCE_ADDRESS_16 and TARGET_ADDRESS_16. These con-
nections carry the actual tester address at run time. Please note that this address is
not provided to the application. If the application needs to discern different testers, sep-
arate connections have to be created. Generic connections are supported for diagnos-
tics over IP and FlexRay diagnostics, and CAN diagnostics using normal fixed or mixed
29 bit addressing formats according to ISO15765-2 [12]. Depending on the actual lay-
out of the CAN IDs, generic connections could also be used for extended or normal and
mixed 11 bit addressing formats. The Dcm is not aware of the actual addressing format
used by CanTp. Several connections may reference the same DcmPdus.
[SWS_Dcm_CONSTR_6044] dGeneric connections shall be consistent. This means
that the MetaDataItems and the PduLength of all referenced PDUs of a DcmDslCon-
nection (DcmDslProtocolRxPduRef, DcmDslProtocolTxPduRef, DcmDslPe-
riodicTxPduRef, DcmDslRoeTxPduRef)are identical.c()
[SWS_Dcm_00848] dThe source address of diagnostic requests received via
a generic connection must be stored. It is provided in the MetaDataItem
SOURCE_ADDRESS_16 provided via Dcm_StartOfReception.c()

60 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00849] Target address for generic connection transmission dIf the

Dcm is about to send a response, response on event, or periodic message for a generic
connection request, the Dcm shall set TARGET_ADDRESS_16 to the value of the
stored source address in the MetaDataPtr in the PduR_DcmTransmit().c(RS_Diag_-
04153)
[SWS_Dcm_01429] dThe source address of diagnostic requests received via a
generic connection shall be provided in the parameter TesterSourceAddress
to the application [SWS_Dcm_01339], [SWS_Dcm_01340], [SWS_Dcm_01341],
[SWS_Dcm_01342], [SWS_Dcm_00692], [SWS_Dcm_00694], [SWS_Dcm_00340],
[SWS_Dcm_00698]).c()
[SWS_Dcm_01347] dThe target address of diagnostic requests received via a generic
connection can be provided in the MetaDataItem TARGET_ADDRESS_16 received via
Dcm_StartOfReception(). In this case, the Dcm shall ignore physical requests where
the target address is not equal to the configured ECU address DcmDspProtocolE-
cuAddr.c(RS_Diag_04153)
[SWS_Dcm_01348] dThe source address of the response transmitted via generic
connections can be read from the configuration parameter DcmDspProtocolE-
cuAddr. It shall be provided to PduR_DcmTransmit() in the MetaDataItem
SOURCE_ADDRESS_16, if that is configured for the transmit PDU.c(RS_Diag_04153)
Note: If different source addresses are required for certain transmitted di-
agnostic messages of the same DcmDslProtocolRow, the MetaDataItem
SOURCE_ADDRESS_16 can be omitted from the PDUs, and the address can then
be configured in the lower layers. The same is possible for physical requests, where
the TARGET_ADDRESS_16 can be omitted from the PDUs.

7.4.4.6 Guarantee timing to tester by sending busy responses

[SWS_Dcm_00024] dIf the Application (or the DSP submodule) is able to perform a
requested diagnostic task, but needs additional time to finish the task and prepare the
response, then the DSL submodule shall send a negative response with NRC 0x78 (Re-
sponse pending) when reaching the response time (DcmDspSessionP2ServerMax
- DcmTimStrP2ServerAdjust respectively DcmDspSessionP2StarServerMax -
DcmTimStrP2StarServerAdjust).c(RS_Diag_04016, RS_Diag_04249)
Rationale for [SWS_Dcm_00024]: The DSL submodule guarantees the response tim-
ing to tester.
[SWS_Dcm_00119] dThe DSL submodule shall send negative responses as required
in [SWS_Dcm_00024] from a separate buffer.c()
Rationale for [SWS_Dcm_00119]: This is needed in order to avoid overwriting the on-
going processing of requests, e.g. the application already prepared response contents
in the diagnostic buffer. The number of negative responses with NRC 0x78 (response
pending) for one diagnostic request can be limited by the configuration parameter

61 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDslDiagRespMaxNumRespPend to avoid endless NRC 0x78 transmission in case

of an application deadlock.
[SWS_Dcm_01567] dThe maximum number of negative responses with NRC 0x78 can
be configured using the optional configuration parameter DcmDslDiagRespMaxNum-
RespPend (see ECUC_Dcm_00693). If this parameter is not configured, the default
amount of negative responses with NRC 0x78 is infinite.c()

7.4.4.7 Support of periodic transmission

The UDS service ReadDataByPeriodicIdentifier (0x2A) allows the tester to request the
periodic transmission of data record values from the ECU identified by one or more
periodicDataIdentifiers.
[SWS_Dcm_00122] dThe Dcm module shall send responses for periodic transmissions
using a separate protocol and a separate buffer of configurable size.c()
The DcmDslPeriodicTransmissionConRef configuration parameter allows linking
the protocol used to receive the periodic transmission request / transmit the periodic
transmission response to the protocol used for the transmission of the periodic trans-
mission messages. Note that multiple DcmTxPduIds can be assigned to the periodic
transmission protocol. The Dcm module respects several restrictions according to the
communication mode:
[SWS_Dcm_00123] dPeriodic transmission communication shall only take place in Full
Communication Mode.c()
Periodic transmission events can occur when not in Full Communication Mode. So the
following requirement exists:
[SWS_Dcm_00125] dThe Dcm module shall discard periodic transmission events be-
side Full Communication Mode and shall not queue it for transmission.c()
[SWS_Dcm_00126] dPeriodic transmission events shall not activate the Full Commu-
nication Mode.c()

7.4.4.8 Support of ROE transmission

With the UDS Service ResponseOnEvent (0x86), a tester requests an ECU to start
or stop transmission of responses initiated by a specified event. Upon registering an
event for transmission, the tester also specifies the corresponding service to respond
to (e.g: UDS Service ReadDataByIdentifier 0x22).
[SWS_Dcm_00595] dThe ROE functionality is enabled only if the container DcmDslRe-
sponseOnEvent exists.c()

62 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.4.4.8.1 ResponseOnEvent StateChar

[SWS_Dcm_00871] dThe Dcm shall support several RoeEvents. Each RoeEvent can
have the states ”ROE cleared”, ”ROE stopped” and ”ROE started”. The transitions
from state to state are described in the following section. The Labels in the figure
below represents the numbers of the sections.c()

stm RoeEv entStateMachine

[10]

Roe cleared [2] Roe stopped

[1] [3]

Initial

[8] [9] [5] [4]

[7]

Roe started

[6]

Figure 7.4: RoeEvent State Chart

7.4.4.8.1.1 Initializing Dcm (1)

[SWS_Dcm_00872] dThe Dcm changes the state of each event to ’ROE cleared’ state
during Dcm_Init.c()

7.4.4.8.1.2 Transition from ’ROE cleared’ to ’ROE stopped’ (2)

[SWS_Dcm_00873] dBy receiving a valid ROE setup request, the RoeEvent which is
addressed in the request changes to the ’ROE stopped’ state (see Table 2).c()
[SWS_Dcm_00874] dIf the RoeEvent was setup with the StorageState set to
’storeEvent’ and no StartResponseOnEvent with StorageState set to ’storeEvent’ and
an EventWindowTime which is active over power cycles or clearResponseOnEvent has
been received afterwards the Dcm will change to ’ROE stopped’ state as soon as the
non-volatile information is available.c()
Note: If an Event is initialized once with StorageState set to ’StoreEvent’, it will
stay initialized until it is cleared by a ClearResponseOnEvent request (see also
[SWS_Dcm_00897]).

63 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00951] dIf for a RoeEvent the configuration parameter DcmDspRoeIni-

tialEventStatus is set to DCM_ROE_STOPPED, the Dcm will switch to ’ROE stopped’
state immediatly in the initialisation.c()
Note: DcmDspRoeInitialEventStatus set defines an initialisation of a RoeEvent
by configuration.

7.4.4.8.1.3 Transition from ’ROE stopped’ to ’ROE cleared’ (3)

[SWS_Dcm_00875] dBy receiving a valid ROE request with the sub-function clear-
ResponseOnEvent (0x06) the RoeEvents change to the ’ROE cleared’ state.c()

7.4.4.8.1.4 Transition from ’ROE stopped’ to ’ROE started’ (4)

[SWS_Dcm_00876] dBy receiving a valid ROE request with the sub-function startRe-
sponseOnEvent (0x05) all stopped RoeEvents change to the ’ROE started’ state.c()
[SWS_Dcm_00902] dAll RoeEvents which have been in ’ROE started’ state when leav-
ing the default session shall change back into ’ROE started’ state when (re-) entering
the default session.c()
[SWS_Dcm_00965] dIf a valid StartResponseOnEvent request is received with a stor-
ageState set to StoreEvent and the EventWindowTime supports the StorageState in a
previous power cycle, the RoeEvent shall change from ’ROE stopped’ state to ’ROE
started’ state as soon as the non-volatile data is available. (This ROEEvent was set to
’ROE stopped’ according to [SWS_Dcm_00951]).c()

7.4.4.8.1.5 Transition from ’ROE started’ to ’ROE stopped’ (5)

[SWS_Dcm_00877] dBy receiving a valid ROE request with the sub-function stopRe-
sponseOnEvent (0x00) the stopped RoeEvents change to the ’ROE stopped’ state.c
()
[SWS_Dcm_00878] dWhen the eventWindowTime times out the stopped RoeEvents
change to the ’ROE stopped’ state.c()
[SWS_Dcm_00879] dBy leaving the current session all started RoeEvents shall
change to the ’ROE stopped’ state.c()
Note: RoeEvents are stopped when the current session is left, independent if the ses-
sion changes from a non-default session to the same or a different non-default session.
By leaving the default session the current active RoeEvents are stopped and stored (in
order to be re-started as soon the session changes back to the default session (see
[SWS_Dcm_00902]).

64 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00952] dIf a ROE request is received with the sub-function OnDTCSta-

tusChange and the RoeEvent is ’ROE started’, the RoeEvent for OnDTCStatusChange
changes to ’ROE stopped’ state and the ServiceToRespondTo shall be triggered by the
DTCStatusMask which is set by the new request.c()

7.4.4.8.1.6 Transition from ’ROE started’ to ’ROE started’ (6)

[SWS_Dcm_00880] dBy receiving a valid ROE request with the sub-function StartRe-
sponseOnEvent (0x05) the Dcm answers positively and stays in ’ROE started’ state. ).c
()

7.4.4.8.1.7 Transition from ’ROE started’ to ’ROE cleared’ (7)

[SWS_Dcm_00884] dBy receiving a valid ROE request with the sub-function clear-
ResponseOnEvent (0x06) all started RoeEvents change to the ’ROE cleared’ state.c
()

7.4.4.8.1.8 Transition from ’ROE cleared’ to ’ROE cleared’ (8)

[SWS_Dcm_00885] dIf all RoeEvents are in ’ROE cleared’ state and a valid stopRe-
sponseOnEvent (0x00) request is received the Dcm shall reject the request with a neg-
ative Response with NRC 0x24 (requestSequenceError).c()
[SWS_Dcm_00886] dIf all RoeEvents are in ’ROE cleared’ state and a valid StartRe-
sponseOnEvent (0x05) request is received the Dcm shall reject the request with a neg-
ative Response with NRC 0x24 (requestSequenceError).c()
[SWS_Dcm_00887] dIf all RoeEvents are in ’ROE cleared’ state and a valid clear-
ResponseOnEvent (0x06) request is received the Dcm answers positively and the
RoeEvents stay in ’ROEcleared’ state.).c()
[SWS_Dcm_00888] dIf the non-volatile data could not be read correctly, all RoeEvents
in ’ROE cleared’ state remain in ’ROE cleared’ state.c()

7.4.4.8.1.9 Transition from ’ROE cleared’ to ’ROE started’ (9)

[SWS_Dcm_00889] dIf the EventWindowTime is active over power cycles and not
timed out, the Dcm shall reactivate all RoeEvents which were active in the default ses-
sion during the last power cycle as soon as the non-volatile information is available.c
()
[SWS_Dcm_00890] dIf a valid StartResponseOnEvent request is received with a stor-
ageState set to StoreEvent and the EventWindowTime supports the StorageState in a

65 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

previous power cycle, the RoeEvent shall change to ’ROE started’ state as soon as the
non-volatile data is available.c()

7.4.4.8.1.10 Transition from ’ROE stopped’ to ’ROE stopped’ (10)

[SWS_Dcm_00891] dIf a RoeEvent is in ’ROE stopped’ state and a valid stopRespon-

seOnEvent (0x00) request is received the Dcm shall respond positively to the request
and stay in the ’ROE stopped’ state.c()
[SWS_Dcm_00953] dIf a ROE request is received with the sub-function OnDTCSta-
tusChange and the RoeEvent is already ’ROE stopped’ the RoeEvent for OnDTCSta-
tusChange shall stay in ’ROE stopped’ state but the event logic shall be updated with
the newly received DTCStatusMask.c()

7.4.4.8.2 ROE sub-functions

[SWS_Dcm_00892] dThe Dcm shall support all ROE sub-functions marked as sup-
ported in Table 7.1.c()
Sub function Sub-function name Kind of ServiceTo Support
ID sub-function RespondTo status
0x00/0x40 stopResponseOnEvent Control Supported
0x01/0x41 onDTCStatusChange Setup 0x19, 0x0E Supported
0x02/0x42 onTimerInterrupt Setup Not supported
0x03/0x43 onChangeOfDataIdentifier Setup 0x22 Supported
0x04 reportActivatedEvents Control Supported
0x05/0x45 StartResponseOnEvent Control Supported
0x06/0x46 clearResponseOnEvent Control Supported
0x07/0x47 onComparisonOfValues Setup Not supported
Other OEM Specific Setup Not supported

Table 7.1: Supported sub function of Response on Event (0x86)

Note: If a user wants to support a sub-function with StorageState bit set, then it has to
be explicitly configured in the DSD. The Dcm will not mask the StorageState bit internally.
[SWS_Dcm_00893] dFor each setup sub function the Dcm shall only support the one
fixed ServiceToRespondTo. The supported ServiceToRespondTo is listed in the table
referred in [SWS_Dcm_00892].c()

7.4.4.8.3 EventWindowTime and StorageState

The EventWindowTime and StorageState are mandatory parameter in every ROE re-
quest. They can be contradicting between the setup request and the related control
request.

66 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00903] dThe Dcm shall evaluate the EventWindowTime from the setup
request.c()
[SWS_Dcm_00894] dhe Dcm shall support in general the EventWindowTimes defined
in Table 7.2.c()
Value Name Active over
PowerCycles
0x02 Infinity Storage State
0x03 CurrentCycle No
0x04 CurrentAndFollowingCycle Yes

Table 7.2: Supported ROE EventWindowTime

[SWS_Dcm_00895] dThe configuration parameter DcmDspRoeEventWindowTime

shall contain a list of all EventWindowTimes supported for this specific Ecu.c()
[SWS_Dcm_00896] dIf the Roe request contains a different EventWindowTime than
configured in DcmDspRoeEventWindowTime the Dcm shall reject the request with a
negative response with the NRC 0x31 (RequestOutOfRange).c()
[SWS_Dcm_01076] dIf the Roe request has a storageState equal to storeEvent and
contains an EventWindowTime that is not infinite, the Dcm shall reject the request with
a negative response with the NRC 0x31 (RequestOutOfRange).c()
[SWS_Dcm_00897] dIf a RoeEvent is setup with StorageState set to storeEvent the
initialization shall be stored non-volatile to be restored in every following driving cycle
until it is cleared (see [SWS_Dcm_00874]).c()
[SWS_Dcm_00898] dA RoeEvent shall change to ’ROE started’ state at the beginning
of each following power cycle until a stopResponseOnEvent request with storage Stor-
ageState set to StoreEvent is received if the RoeEvent fulfills all following conditions
:
• The RoeEvent was started in default session
• The StartResponseOnEventRequest has a storageState set to ’StoreEvent’
• The setup request has the EventWindowTime inifinity and the storageState was
set to ’StoreEvent’.
c()
[SWS_Dcm_00905] dThe EventWindowTime will end at the end of the current power
cycle if all of the following conditions are fulfilled:
• The EventWindowTime is set to infinity (0x02) during the setup request
• The RoeEvent was started in default-session
• The storageState was not set in the StartResponseOnEvent request
c()

67 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00900] dIf a RoeEvent set up with the EventWindowTime set to Cur-

rentAndFollowingCycle is started in default session, the EventWindowTime shall end
at the end of the next power cycle or with a clearResponseOnEvent/stopResponseOn-
Event request.c()
[SWS_Dcm_00901] dIf a RoeEvent set up with the EventWindowTime set to Current-
Cycle is started in default session, the EventWindowTime shall end at the end of the
current power cycle or with a clearResponseOnEvent/stopResponseOnEvent.c()
[SWS_Dcm_00906] dIf ResponseOnEvent is started in a non-default session, the
EventWindowTime ends if one of the following conditions is fulfilled:
• The power cycle ends
• Receiving a clearResponseOnEvent request
• Receiving a stopResponseOnEvent request
• With any session change.
c()
[SWS_Dcm_00907] dIf the EventWindowTime times out and the power cycle is not
ended, the Dcm shall send a final positive Response to the setup request.c()
For the EventWindowTime infinity (0x02), ThisCycle (0x03), ThisAndNextCycle (0x04)
the Dcm will not send a final response because these EventWindow Times will end at
the end of an power cycle. There will also no final response if the session changes or
the service is stopped with a ’stopResponseOnEvent’ subfunction.

7.4.4.8.4 Pre-configuration of ResponseOnEvent

[SWS_Dcm_00908] dThe Dcm shall only support Roe requests which where pre-
configured in the configuration.c()
Note: The pre-configuration gives the Dcm the freedom to optimized not configured
requests.
[SWS_Dcm_00909] dThe Dcm supports the configuration container DcmDspRoe to
configure all supported ResponseOnEvent setup requests.c()
[SWS_Dcm_00954] Pre-configuraton of ROE events dIf DcmDspRoeIni-
tialEventStatus is set to DCM_ROE_STOPPED, the Dcm shall behave according
RoeEvent set-up:
• StorageState set to "StoreEvent"
• EventWindowTime set to "infinity"
• DTCStatusMask set to value configured in DcmDspRoeDTCStatusMask in case
of onDTCStatusChange and

68 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• DID set to the value given with DcmDspRoeDidRef in case of onChangeOf-

DataIdentifier
c()
[SWS_Dcm_01323] dLikewise, when responding to the reportActivatedEvents (0x04)
subfunction of the ResponseOnEvent (0x86) service, preconfigured events shall have
the storageState bit set within the corresponding eventTypeOfActiveEvent byte.c()
According to [SWS_Dcm_00954] and [SWS_Dcm_00897], the pre-configuration of
RoeEvents shall behave the same like received a received setup and start request in
previous driving cycles. If the storageState is set in the start/stop/clearedResponseOn-
EventRequest the pre configuration will be replaced with the newly received request.

7.4.4.8.5 Handling of event-trigger

7.4.4.8.5.1 ROE event-trigger onDTCStatusChange (0x01)

If a RoeEvent is in ’ROE started’ state and it is configured to onDTCStatusChange (see

container DcmDspRoeEvent), the Dcm triggers a ServiceToResponseTo as soon as
the Dem is reporting a DTCStatusChange which fits to the requested DTCStatusMask.
According to [SWS_Dcm_00909], the Dcm only supports preconfigured ROE requests.
Therefore the container DcmDspRoeOnDTCStatusChange needs to be configured if
onDTCStatusChange shall be used.
[SWS_Dcm_00912] dIf the state of one RoeEvent that is configured for onDTC-
StatusChange changes to ’ROE started’ the Dcm shall evaluate the callback Dcm_-
DemTriggerOnDTCStatus.c()
[SWS_Dcm_00913] dIf the state of the RoeEvent, configured to OnDTCStatusChange,
leaves ’ROE started’ the Dcm shall ignore the callback Dcm_DemTriggerOnDTCSta-
tus.c()
[SWS_Dcm_01410] dIn case a request to clear the EventMemory is processed, the
Dcm shall ignore the callback Dcm_DemTriggerOnDTCStatus.c()
[SWS_Dcm_00914] dIf the state of the RoeEvent is ’ROE started’ for the sub-
function OnDTCStatusChange shall trigger a serviceToRespondTo if Dcm_DemTrig-
gerOnDTCStatus is called and the DTCStatusNew fits to the corresponding DTCSta-
tusMask.c()
[SWS_Dcm_00915] dIf an event is trigger for onDTCStatusChange, the Dcm shall exe-
cute a serviceToResponseTo 0x19 0x0E, if the DTCStatusNew fits to the corresponding
DTCStatusMask.c()
[SWS_Dcm_CONSTR_6054] Existence of DTCStatusMask dDcmDspRoeDTCSta-
tusMask shall be present if DcmDspRoeInitialEventStatus is set to DCM_ROE_-
STOPPED.c()

69 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.4.4.8.5.2 ROE event-trigger onChangeOfDataIdentifier (0x03)

If a RoeEvent is in ’ROE started’ state and it is configured to onChangeOfDataIdenti-

fier (see container DcmDspRoeEvent) , the Dcm triggers a ServiceToResponseTo as
soon as a SWC or a CDD is reporting a change of the DID referenced by DcmD-
spRoeDidRef (SWC or CCD reports DID change by call of Dcm_TriggerOnEvent).
According to [SWS_Dcm_00909], the Dcm only supports preconfigured ROE requests.
Therefore the Did in the ROE setup request with onChangeOfDataIdentifier has to be
linked as DcmDspRoeDidRef in the onChangeOfDataIdentifier configuration.
[SWS_Dcm_00918] dIf a ResponseOnEvent is requested as onChangeOfDataIden-
tifier and the requested Did is not referred as DcmDspRoeDidRef for any DcmD-
spRoeEvent the Dcm shall reject the request with a negative response with NRC 0x31
RequestOutOfRange.c()
[SWS_Dcm_00920] dIf Dcm_TriggerOnEvent is called and the passed RoeEvent is
active, the Dcm shall trigger an Event for this RoeEvent.c()
[SWS_Dcm_00921] dIf an event is triggered for onChangeOfDataIdentifier, the Dcm
shall execute a serviceToResponseTo 0x22 with the Did which is referred for this
RoeEvent (DcmDspRoeDidRef) .c()

7.4.4.8.6 Trigger a ServiceToRespondTo

[SWS_Dcm_00922] dIf a ServiceToRespondTo is triggered by a RoeEvent the Dcm

shall execute the ServiceToRespondTo as normal diagnostic service according to the
figure ’General server response behavior’ of ISO14229-1 [1].c()
[SWS_Dcm_00558] dIf a ServiceToRespondTo is triggered while the Dcm is already
executing a request on a different diagnostic Protocol the Dcm shall postpone the Ser-
viceToRespondTo until the execution of the service is finalized.c()
[SWS_Dcm_00923] dThe Dcm shall only process the last ServiceToRespondTo. If
already a ServiceToRespondTo is postponed due to another service execution the new
respond shall overwrite the previous trigger.c()
[SWS_Dcm_00924] dIf a ServiceToRespondTo is executed while a Request on a dif-
ferent diagnostic protocol is received the ServiceToRespondTo shall be canceled.c()
[SWS_Dcm_00925] dIf ServiceToRespondTo are pending when the RoeEvent
changes to the ’ROE cleared’ state or ’ROE stopped’ state the pending RoeEvent will
be removed.c()
[SWS_Dcm_00127] dIf the UDS service ResponseOnEvent (0x86) is received with the
subservice StartResponseOnEvent, then the DSP sub-module shall store the respec-
tive configured connectionId of the received RxPduId for all RoeEvents which will be
started until the eventWindowTime times out.c()

70 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00128] dThe DSP submodule shall forward this stored connectionId as pa-
rameter in the DslInternal_ResponseOnOneEvent() function, where it is used to trigger
a serviceToRespondTo.c()
Note: The Dcm stores the connectionId of the protocol where the ROE request is re-
ceived, independent if the serviceToResponseTo is sent to a same or a different Tx-
PduId. The connectionId links always the correct TxPduId, because there is only one
TxPduId for ServiceToRespondTo linked to one protocol (see ConfigurationParameter
DcmDslROEConnectionRef). If RoeEvents are active over power cycles the connec-
tionId needs to be stored over power cycles.

7.4.4.8.7 Send a ServiceToRespondTo

The Dcm supports the transmission from ServiceToResponseTo on the same TxPduId
like the ROE response is send (TYPE 1) or on a different TxPduId (TYPE 2).
[SWS_Dcm_00131] dThe configured protocol buffer shall be used for transmission of
the ROE messages (as the reception shall use a separate protocol, a separate buffer
needs to be used for reception).c()
[SWS_Dcm_00926] dIf a ROE request is received on a protocol DcmDslMainConnec-
tion, the Dcm shall send the ServiceToRespondTo on the protocol which is referred
as DcmDslROEConnectionRef.c()
Note: if the EventWindowTime ist active over more than this power cycle, the Dcm
has to store the protocol where the event was started.[SWS_Dcm_00927] dIf the re-
ferred Protocol for ResponseOnEvent (DcmDslROEConnectionRef) is configured for
TYPE1 the Dcm shall send the ServiceToRespondTo to the same TxPduID as the ROE
response is send to.c()
[SWS_Dcm_00928] dIf the referred Protocol for ResponseOnEvent (DcmDslROECon-
nectionRef) is configured for TYPE2 the Dcm shall send the ServiceToRespondTo to
the configured TxPduID (see configuration parameter DcmDslRoeTxPduRef).c()
[SWS_Dcm_00132] dThe content of the pMsgContext pointer (ROE message) shall
be copied into the buffer.c()
[SWS_Dcm_00133] dROE communication shall only be performed in Full Communica-
tion Mode. The Dcm shall check the communication mode of the DcmDslProtocol-
ComMChannelRef in the DcmDslMainConnection.c()
[SWS_Dcm_00134] dROE events shall be disabled in any other Communication Mode
except for the Full Communication Mode.c()
[SWS_Dcm_00135] dROE events occurring in a communication mode different from
Full Communication Mode shall be discarded and not queued for later transmission.c()
[SWS_Dcm_00136] dROE events requested by the Application shall not activate the
Full Communication Mode.c()

71 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01534] Authentication check for service to respond to dOn transmis-

sion of the service to respond to, the Dcm shall perform the service authentication
checks and send a positive response only for services that have granted access to that
connection.c(RS_Diag_04230)
[SWS_Dcm_CONSTR_6025] Reference to DcmDslResponseOnEvent connection
dOnly one DcmDslROEConnectionRef shall reference DcmDslResponseOnEvent
connection.c()
[SWS_Dcm_CONSTR_6056] Dependency for DcmDslProtocolTransType d
DcmDslProtocolTransType shall be only present if the Dcm_ProtocolType is
configured to DCM_ROE_ON_CAN or DCM_ROE_ON_FLEXRAY or DCM_ROE_ON_IP.c()

7.4.4.8.7.1 Roe transmission cycle

[SWS_Dcm_00601] dThe Dcm module shall respect a minimum time between two (2)
consecutive Roe transmissions (see configuration parameter DcmDspRoeInterMes-
sageTime)c()

7.4.4.8.8 ResponseOnEvent in multiple client environments

[SWS_Dcm_00929] dIf at least one RoeEvent is in ’ROE started’ state the Dcm shall al-
ways process ROE request with the sub-function clearResponseOnEvent independent
of the DcmDslProtocol where the request is received.c()
[SWS_Dcm_00930] dIf at least one RoeEvent is in ’ROE started’ state the Dcm shall
always process ROE request with the sub-function stopResponseOnEvent independent
of the DcmDslProtocol where the request is received.c()
[SWS_Dcm_00940] dIf at least one RoeEvent is in ’ROE started’ state the Dcm shall
reject all ROE request received on a different DcmDslProtocol than the protocol
where the RoeEvents were started with an NRC 0x22 (ConditionsNotCorrect), except
for [SWS_Dcm_00929] and [SWS_Dcm_00930].c()
[SWS_Dcm_01045] dOnly TYPE2 messages will support parallel execution of Diag-
nosis response.c()

7.4.4.9 Support of segmented response (paged-buffer)

[SWS_Dcm_00028] dIf enabled (DcmPagedBufferEnabled=TRUE), the Dcm mod-

ule shall provide a mechanism to send responses larger than the configured and allo-
cated diagnostic buffer.c()

72 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_CONSTR_6055] Dependency for DcmDslProtocolMaximumRe-

sponseSize dDcmDslProtocolMaximumResponseSize shall be only present if
DcmPagedBufferEnabled is set to TRUE.c()
[SWS_Dcm_01058] dIf DcmPagedBufferEnabled == TRUE and the generated Re-
sponse for a Request is longer than DcmDslProtocolMaximumResponseSize, the
Dcm shall respond with NRC 0x14 (DCM_E_RESPONSETOOLONG).c()
[SWS_Dcm_01059] dIf DcmPagedBufferEnabled == FALSE and the generated Re-
sponse for a Request is longer than Dcm_MsgContextType structure element resMax-
DataLen, the Dcm shall respond with NRC 0x14 (DCM_E_RESPONSETOOLONG) .c
()
With paged-buffer handling the ECU is not forced to provide a buffer, which is as large
as the maximum length of response. Please note:
• paged-buffer handling is for transmit only - no support for reception.
• paged-buffer handling is not available for the Application (DCM-internal use only).
[SWS_Dcm_01186] dThe Dcm shall provide the correct amount of Data requested by
the TP or return BUFREQ_E_BUSY in case the requested amount of data is not avail-
able.c(RS_Diag_04147)
Note: In case the requested amount of data is not available, the Dcm should fill up the
paged buffer immediately.

7.4.4.10 Support of ResponsePending response triggered by the Application

In some cases, e.g. in case of routine execution, the Application needs to request an
immediate NRC 0x78 (Response pending), which shall be sent immediately and not
just before reaching the response time (P2ServerMax respectively P2*ServerMax).
When the Dcm module calls an operation and gets an error status
DCM_E_FORCE_RCRRP, the DSL submodule will trigger the transmission of a
negative response with NRC 0x78 (Response pending). This response needs to be
sent from a separate buffer, in order to avoid overwriting the ongoing processing of the
request.

7.4.4.11 Manage security level

[SWS_Dcm_00020] dThe DSL submodule shall save the level of the current active
security level.c(RS_Diag_04005)
For accessing this level, the DSL submodule provides interfaces to:
• get the current active security level: Dcm_GetSecurityLevel
• set a new security level: DslInternal_SetSecurityLevel()

73 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00033] dDuring Dcm initialization the security level is set to the value 0x00
(DCM_SEC_LEV_LOCKED).c(SRS_BSW_00101, RS_Diag_04005)
[SWS_Dcm_00139] dThe DSL shall reset the security level to the value 0x00 (i.e. the
security is enabled) under one of the following conditions: - if a transition from any
diagnostic session other than the defaultSession to another session other than the de-
faultSession (including the currently active diagnostic session) is performed or - if a
transition from any diagnostic session other than the defaultSession to the defaultSes-
sion (DslInternal_SetSecurityLevel()) (initiated by UDS Service DiagnosticSessionCon-
trol (0x10) or S3Server timeout) is performed.c()
Only one security level can be active at a time.
[SWS_Dcm_01329] dOn every security level change the Dcm shall update the Mod-
eDeclarationGroup DcmSecurityAccess with the new security level.c()
[SWS_Dcm_CONSTR_6083] Dependency on DcmDspSecurityAttemptCoun-
terEnabled dIf DcmDspSecurityNumAttDelay is not configured, the DcmDspSe-
curityAttemptCounterEnabled on the same DcmDspSecurityRow shall be set
to FALSE.c(RS_Diag_04005)

7.4.4.11.1 Initialization sequence

[SWS_Dcm_01154] dAt initialization, for each DcmDspSecurityRow entry for which

the DcmDspSecurityAttemptCounterEnabled configuration parameter is set to
TRUE, the corresponding Xxx_GetSecurityAttemptCounter shall be called in or-
der to get the value of the AttemptCounter for each of these DcmDspSecurityRow
entries.c()
[SWS_Dcm_01156] dIf Xxx_GetSecurityAttemptCounter has returned
E_NOT_OK the attempt counter shall be set to the value configured in DcmD-
spSecurityNumAttDelay of the according SecurityLevel.c()
[SWS_Dcm_01351] dIf any Xxx_GetSecurityAttemptCounter opera-
tion returns a DCM_E_PENDING value, the Dcm shall interrupt calling the
Xxx_GetSecurityAttemptCounter() in order to resume this chain of calls within
the next Dcm_MainFunction() cycle.c()
Note: this may be the case when these values are stored within some specific non-
volatile memory.
[SWS_Dcm_CONSTR_6076] Dependency for DcmDspSecurityGetAttempt-
CounterFnc dDcmDspSecurityGetAttemptCounterFnc shall be present only if
DcmDspSecurityUsePort is set to USE_ASYNCH_FNC and DcmDspSecurityAt-
temptCounterEnabled is set to TRUE.c()
[SWS_Dcm_01352] dIf the delay after the first call of the Dcm_MainFunction() which
is configured in DcmDspSecurityMaxAttemptCounterReadoutTime has been
reached and all the Xxx_GetSecurityAttemptCounter have not been called

74 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

yet (i.e. one operation has returned a DCM_E_PENDING status in the previous
Dcm_MainFunction() cycle), the pending operation shall be cancelled by a call with
the OpStatus set to DCM_CANCEL.c()
[SWS_Dcm_01353] dIn the conditions of [SWS_Dcm_01352], the AttemptCounters of
remaining security levels (which have not been obtained via the calls to their Xxx_Get-
SecurityAttemptCounter) shall be initialized with the value configured in DcmD-
spSecurityNumAttDelay of the according SecurityLevel.c()
[SWS_Dcm_01354] dWhile not all Xxx_GetSecurityAttemptCounter operations
have returned a final status and the operation chain has not been cancelled, the con-
ditionsNotCorrect (0x22) NRC shall be returned to any SecurityAccess (0x27) request-
Seed subfunction request.c()
[SWS_Dcm_01355] dOnce all the AttemptCounter values have been successfully or
unsuccessfully retrieved (all the Xxx_GetSecurityAttemptCounter() operations have
been executed and have returned a final, non-PENDING error value or the opera-
tion chain has been cancelled), if at least one of the restored AttemptCounter val-
ues is greater than or equal to the DcmDspSecurityNumAttDelay configured for
its corresponding DcmDspSecurityRow, the Dcm shall start the SecurityDelayTimer
with the higher value of DcmDspSecurityDelayTimeOnBoot / DcmDspSecurity-
DelayTime of the according DcmDspSecurityRow.c()
[SWS_Dcm_01356] dA timer (DcmDspSecurityDelayTime, DcmDspSecurity-
MaxAttemptCounterReadoutTime) which is configured with 0 shall be considered
to have timed out instantaneously when it is started, i.e. shall have no delay effect.c()
[SWS_Dcm_CONSTR_6074] Dependency for DcmDspSecurityMaxAttempt-
CounterReadoutTime dDcmDspSecurityMaxAttemptCounterReadoutTime
shall be a multiple and at minimum equal to DcmTaskTime.c()

7.4.4.11.2 AttemptCounter update

[SWS_Dcm_01357] dA successful sendKey subfunction request or an expired Securi-

tyDelayTimer shall reset that security level’s specific AttemptCounter.c()
[SWS_Dcm_01155] dThe Dcm shall call Xxx_SetSecurityAttemptCounter() (in case
the configuration parameter DcmDspSecurityAttemptCounterEnabled for the ac-
cording DcmDspSecurityRow is set to TRUE) when the Dcm has changed the attempt
counter to inform the application about the counter change.c()
[SWS_Dcm_CONSTR_6078] Dependency for DcmDspSecuritySetAttempt-
CounterFnc dDcmDspSecuritySetAttemptCounterFnc shall be present only if
DcmDspSecurityUsePort is set to USE_ASYNCH_FNC and the DcmDspSecurity-
AttemptCounterEnabled set to TRUE.c()

75 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.4.4.12 Manage session state

[SWS_Dcm_00022] dThe DSL submodule shall save the state of the current active
session.c(RS_Diag_04006)
For accessing this variable, the DSL submodule provides interfaces to:
• get the current active session: Dcm_GetSesCtrlType
• set a new session: DslInternal_SetSesCtrlType()
[SWS_Dcm_00034] dDuring Dcm initialization, the session state is set to the value
0x01 ("DefaultSession").c(SRS_BSW_00101)
[SWS_Dcm_01062] dThe call to Dcm_ResetToDefaultSession allows the appli-
cation to reset the current session to Default session and invokes the mode switch
of the ModeDeclarationGroupPrototype DcmDiagnosticSessionControl by calling
SchM_Switch_<bsnp>_DcmDiagnosticSessionControl(RTE_MODE_DcmDiagnostic
SessionControl_DCM_DEFAULT_SESSION).c()
Example: Automatic termination of an extended diagnostic session upon exceeding of
a speed limit.

7.4.4.13 Manage authentication state

The Dcm provides means for authenticated diagnostics. The DSL sub-module provides
an authentication state per diagnostic connection. It initializes this state upon startup
and takes care about fallback into non-authenticated states if the connection is idle for
some time.
[SWS_Dcm_01477] Authentication state per connection dThe Dcm shall provide an
authentication state per configured DcmDslConnection.c(RS_Diag_04230)
[SWS_Dcm_01478] Mode declaration group per authentication state dThe Dcm
shall provide the state of each authentication state via the ModeDeclarationGroupPro-
totype DcmAuthentication_<ConnectionName>.c(RS_Diag_04230)
The Dcm maintains an authentication state and mirrors this state to the mode dec-
laration group DcmAuthentication_<ConnectionName>. This mode declaration group
is intended to be changed only by the Dcm, however applications changing this state
have no influence on the Dcm authentication state.
[SWS_Dcm_01479] Authentication states dThe Dcm shall support per connection
the two authentication states:c(RS_Diag_04230)
• deauthenticated
• authenticated

76 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Upon startup, the Dcm is in deauthenticated state or restores the persisted state. A
transition to authenticated state can only be done after the client successfully exe-
cuted the authentication sequence. In some use cases as in production, a frequent
power-on/power off sequence is performed. To keep the achieved authentication state
over the power off, there is a dedicated mode rule requesting the Dcm to persist the
authenticated state.
[SWS_Dcm_01480] Initialization of authentication state dIf DcmDspAuthentica-
tionPersistStateModeRuleRef is not configured or the mode rule referenced
by DcmDspAuthenticationPersistStateModeRuleRef is evaluated to false, the
Dcm shall initialize within Dcm_Init all authentication states to deauthenticated state.c
(RS_Diag_04230)
[SWS_Dcm_01481] Initialization of persisted authentication states dIf the mode
rule referenced by DcmDspAuthenticationPersistStateModeRuleRef is eval-
uated to true, the Dcm shall initialize the persisted authentication state including role
and white list on each connection.c(RS_Diag_04230)
Transitions between authenticated states are controlled by both DSL and DSP sub-
modules. The DSL sub-module is in charge for fallback of authenticated state into
deauthenticated state. The DSP sub-module is in charge for transition changes trig-
gered from a client by diagnostic services.

Figure 7.5: Authenticated state transitions without persistent states

[SWS_Dcm_01482] Fallback to deauthenticated session on idle connection dThe

Dcm shall make a transition from authenticated into deauthenticated state for a config-
ured connection if the following conditions apply:
• The Dcm was in default session when the last diagnostic response was send on
that connection and

77 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• DcmDspAuthenticationDefaultSessionTimeOut is configured and no

valid diagnostic request was received on that connection for DcmDspAuthenti-
cationDefaultSessionTimeOut seconds after the last Dcm_TpTxConfir-
mation on that connection.
c(RS_Diag_04230)
[SWS_Dcm_01483] Fallback to deauthenticated session on S3server timeout dIf
the Dcm is in a non-default session and a S3server timeout occurs, the Dcm shall
perform a transition from authenticated into deauthenticated state on the authentication
state assigned to that connection which was in a non-default session.c(RS_Diag_-
04230)
[SWS_Dcm_01484] Clearing persisted authentication state dIf the authentication
state of a connection performs a transition to deauthenticated state, the Dcm shall
clear all persisted authentication information on that connection.c(RS_Diag_04230)
[SWS_Dcm_01485] Reaction of fallback into deauthenticated state dUpon a tran-
sition from authenticated into deauthenticated state, the Dcm shall discard the current
role, white list and use the configured deauthentication role from DcmDspAuthenti-
cationDeauthenticatedRole.c(RS_Diag_04230)
In some use cases, it is desirable that the application set the role instead of using
a diagnostic service with its potentially time-consuming certificate parsing. The Dcm
provides the API Dcm_SetDeauthenticatedRole to overwrite the configured deau-
thentication role. The overwritten role is only valid in deauthenticated state will not be
persisted and is overwritten by a role provided by certificates via service 0x29.
[SWS_Dcm_01486] Default authentication role set from SWC dIf a connection is
in deauthenticated state and the API Dcm_SetDeauthenticatedRole is called, the
Dcm shall use the provided deauthenticatedRole as new role per deauthenticated state
for this connection.c(RS_Diag_04230)
[SWS_Dcm_01487] Setting deauthenticated role by SWC only in deauthenticated
state dThe Dcm shall process a call of Dcm_SetDeauthenticatedRole only if the
connection is in deauthenticated state.c(RS_Diag_04230)
[SWS_Dcm_01488] Lifetime of deauthenticated role by SWC dA deauthenticated
role set by Dcm_SetDeauthenticatedRole is discarded when that connection per-
forms a transition authenticated state.c(RS_Diag_04230)
[SWS_Dcm_01489] No persistency for deauthenticated roles by SWC dAt startup
the ECU shall always use the deauthentication state configured in DcmDspAuthen-
ticationDeauthenticatedRole.c(RS_Diag_04230)

7.4.4.14 Keep track of active non-default sessions

[SWS_Dcm_00140] dWhenever a non-default session is active and when the ses-

sion timeout (S3Server) is reached without receiving any diagnostic request, the DSL

78 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

submodule shall reset to the default session state ("DefaultSession", 0x01) and in-
voke the the mode switch of the ModeDeclarationGroupPrototype DcmDiagnosticSes-
sionControl by calling SchM_Switch_<bsnp>_DcmDiagnosticSessionControl(RTE_
MODE_DcmDiagnosticSessionControl_DEFAULT_SESSION) .c()
Note: <bsnp> is the BSW Scheduler Name Prefix
The start / stop of S3Server timeout timer is processed as follows:
[SWS_Dcm_00141] d
Subsequent start:
• Completion of any final response message or an error indication (Dcm_TpTx-
Confirmation: confirmation of complete PDU or indication of an error)
• Completion of the requested action in case no response message (positive and
negative) is required / allowed.
• Indicates an error during the reception of a multi-frame request message.(Dcm_-
TpRxIndication: indication of an error)
Subsequent stop:
• Start of a multi-frame request message (Dcm_StartOfReception: indicates
start of PDU reception)
• Reception of single-frame request message. (Dcm_StartOfReception: indi-
cates start of PDU reception)
"Start of S3Server" means reset the timer and start counting from the beginning.c(RS_-
Diag_04249)

7.4.4.15 Allow to modify timings

[SWS_Dcm_00027] dThe Dcm module shall handle the following protocol tim-
ing parameters in compliance with ISO14229-2 [10]: P2ServerMin, P2ServerMax,
P2*ServerMin, P2*ServerMax, S3Serverc(RS_Diag_04015, RS_Diag_04249)
[SWS_Dcm_00143] dP2min / P2*min and S3Server shall be set to defined values:
P2min = 0ms, P2*min = 0ms, S3Server = 5s.c(RS_Diag_04015, RS_Diag_04249)
These protocol timing parameters have influence on the session layer timing (no influ-
ence on Transport Layer timing). Some of these timing parameters can be modified
while protocol is active with the following means:
• UDS Service DiagnosticSessionControl (0x10)
• UDS Service AccessTimingParameter (0x83)
The DSL submodule provides the following functionalities to modify the timing parame-
ters:

79 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• Provide the active timing parameters,

• Set the new timing parameters. Activation of new timing values is only allowed
after sending the response.

7.4.4.16 Handling of different diagnostic protocols

It is necessary to distinguish between different diagnostic protocols (e.g. OBD, en-

hanced diagnosis ...).
[SWS_Dcm_01365] dIf the API Dcm_GetActiveProtocol is called, the Dcm shall
return the active UDS protocol as Dcm_ProtocolType in the ActiveProtocol pa-
rameter.c(RS_Diag_04163)
[SWS_Dcm_01366] dIf only an OBD protocol or no protocol is started and the API
Dcm_GetActiveProtocol is called, the Dcm shall return with ActiveProtocol pa-
rameter set to DCM_NO_ACTIVE_PROTOCOL.c(RS_Diag_04163)
Note: The Dcm_GetActiveProtocol API doesn’t supply information about running
OBD protocols.

7.4.4.16.1 Different service tables

For the different protocols a different set of allowed diagnostic services is valid (e.g.
the UDS commands for the enhanced diagnosis, the OBD mode services for the OBD
protocol). It is possible to create different service tables and link them to the diagnostic
protocol.
[SWS_Dcm_00035] dWith every protocol initialization, the DSL submodule sets a link
to the corresponding service table (see configuration parameter DcmDslProtocol-
SIDTable).c(SRS_BSW_00101)
The DSD submodule uses this link for further processing of diagnostic requests.

7.4.4.16.2 Prioritization of protocol

The configuration parameter DcmDslProtocolPriority makes it possible to give

each protocol its own relative priority. Possible use case: There are ECUs, communi-
cating with a vehicle-internal diagnostic tester (running on enhanced diagnosis) and a
vehicle-external OBD tester. The OBD communication must have a higher priority than
the enhanced diagnosis.
[SWS_Dcm_00015] dA protocol with higher priority is allowed to preempt the already
running protocol.c(RS_Diag_04021)

80 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Differentiation of diagnostic protocols is possible, because of different DcmDslProto-

colRxPduId values (configured per protocol, see configuration parameter DcmDsl-
ProtocolRxPduRef) referenced in the protocol configuration.

7.4.4.16.3 Preemption of protocol

[SWS_Dcm_00459] dIf a running diagnostic request is preempted by a higher pri-

ority request (of another protocol), the DSL submodule shall call all configured
Xxx_StopProtocol() functions (see configuration parameter DcmDslCallbackDCMRe-
questService).c()
[SWS_Dcm_01144] dProtocol preemption can’t be activated with a Concurrent
TesterPresent of a higher priority protocol (see also [SWS_Dcm_01146]).c()
[SWS_Dcm_00079] dIn order to cancel pending transmission in lower-layer, related to
the lower priority request, the Dcm module shall call PduR_DcmCancelTransmit () with
the following parameters: PduId: the id of the Pdu to be canceledc()
[SWS_Dcm_00460] dWhen PduR_DcmCancelTransmit() returns E_NOT_OK, the Dcm
module shall assume that the ongoing transmission cannot be cancelled and shall not
retry to cancel the transmit request. The current protocol shall be stopped and the new
one started.c()
[SWS_Dcm_01046] dIf a running diagnostic request is preempted by a higher priority
request (of another protocol), the Dcm shall cancel all external pending operations with
Dcm_OpStatus set to DCM_CANCELc()
[SWS_Dcm_01047] dIn case an operation to the Dem is pending and the new request
also requires an interaction with the Dem, the Dcm shall accept the new request and
call the corresponding Dem API with the parameters from the new request.c()
[SWS_Dcm_00575] dIn order to cancel pending reception in lower-layer, related to the
lower priority request, the Dcm module shall call PduR_DcmCancelReceive () with the
following parameters: PduId: the id of the Pdu to be canceledc()
[SWS_Dcm_00576] dWhen PduR_DcmCancelReceive () returns E_NOT_OK, the Dcm
module shall assume that the ongoing reception cannot be cancelled and shall not retry
to cancel the receiverequest. The current protocol shall be stopped and the new one
started.c()
[SWS_Dcm_00625] dA Low-priority or same-priority request can preempt a higher
priority protocol if this higher priority protocol is in default session and no active re-
quest is in execution phase. In this case the DSL submodule shall call all configured
Xxx_StopProtocol() functions (see configuration parameter DcmDslCallbackDCMRe-
questService).c()
[SWS_Dcm_00728] dThe handling of protocols with equal priority shall be possible.c()

81 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00727] dIf a diagnostic request is already running and a second request

(ClientB) can not be processed (e.g.due to priority assessment), the response be-
haviour depends on the configuration option parameter DcmDslDiagRespOnSecond-
DeclinedRequest (see [SWS_Dcm_00914]_Conf). If this configuration parameter is
TRUE, a negative response with NRC 0x21 (BusyRepeatRequest) shall be issued for
the second request (see [SWS_Dcm_00788] and [SWS_Dcm_00789]). If the config-
uration parameter is FALSE, no response shall be issued (see [SWS_Dcm_00790]).c
()
[SWS_Dcm_00729] dIn case of multiple clients with different PduIDs which are re-
questing the same protocol, as all the connections of the same protocol are having the
same priority, a second request (with the different RxPduId) will not be processed. If the
configuration parameter DcmDslDiagRespOnSecondDeclinedRequest is TRUE, a
negative response with NRC 0x21 (BusyRepeatRequest) shall be issued for the second
request. If the configuration parameter is FALSE, no response shall be issued.c()
Note:
• A multitude of RxPduIDs may be configured per DcmDslProtocol
• These RxPduIDs may be themselves connected to different Testers via the PduR
configuration
• This means that many Testers may be configured for the same Protocol
• And this represents a non-UDS extension/use case. In order to have a UDS-
compliant flow, there should be one DcmDslProtocol instance per Tester.
[SWS_Dcm_01050] dIn case of diagnostic parallel requests, with same / lower pri-
ority than the active request then the ComM APIs (ComM_DCM_ActiveDiagnostic,
ComM_DCM_InactiveDiagnostic) shall not be called.c()

7.4.4.16.4 Parallel OBD and UDS protocol processing

[SWS_Dcm_01367] dThe Dcm shall process incoming OBD requests in parallel to

a running UDS request. In this case the protocol priority check according to
[SWS_Dcm_00015] is skipped and no protocol pre-emption is done.c(RS_Diag_-
04163)
With the container DcmDslProtocolRow, the Dcm configuration supports multiple pro-
tocols. Each protocol has a configured DcmDemClientRef defining the Dem client in-
teracting with the Dem. This client Id allows the Dem to distinguish between concurrent
calls of the Dcm of the same function or set of functions to process a certain request.
[SWS_Dcm_01369] dWhile processing a diagnostic request received from a given pro-
tocol, the Dcm shall determine the DcmDemClientRef of the DcmDslProtocolRow
of the processed protocol. The Dcm shall use this value in all Dem API calls that have a
ClientId as parameter.c(RS_Diag_04162)

82 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01370] dThe Dcm shall internally serialise all asynchronous C/S interface
calls by the same port interface between the OBD and UDS protocol processors and
return a pending to the re-entrant caller.c(RS_Diag_04162)
[SWS_Dcm_01371] dIf the Dcm received an OBD request and the Dcm is processing
a diagnostic service in a non-default session, the Dcm shall cancel the running UDS
request, make a transition into default session and process the OBD request.c(RS_-
Diag_04162)
[SWS_Dcm_01372] dIf the Dcm processes an OBD request and the Dcm is receiving an
UDS diagnostic request to change in a non-default session, the Dcm shall delay the UDS
request until the OBD service is finished according to [SWS_Dcm_01371]. After the
OBD service is finished, the Dcm shall make a transition into the requested non-default
session.c(RS_Diag_04162)

7.4.4.16.5 Detection of protocol start

[SWS_Dcm_00036] dWith first request of a diagnostic protocol, the DSL submodule

shall call all configured Xxx_StartProtocol() functions (see configuration parameter
DcmDslCallbackDCMRequestService).c(SRS_BSW_00101)
Inside this function, the Application can examine the environment conditions and en-
able/disable further processing of the protocol.
[SWS_Dcm_00144] dAfter all Xxx_StartProtocol() functions have returned E_OK
(meaning all components have allowed the start of the protocol), the default timing
parameters are loaded from the default session configuration (see configuration pa-
rameter DcmDspSessionRow).c(RS_Diag_04015)
[SWS_Dcm_CONSTR_6000] Harmonize the naming between interfaces and
modes dThe shortname of DcmDspSessionRow shall match names of
Dcm_SesCtrlType and of the mode declarations of DcmDiagnosticSessionControl. The
"DCM_" prefix is mandatory for all shortnames.c()
[SWS_Dcm_CONSTR_6001] Provide standardized names for ISO standardized
diagnostic sessions dThe following values of DcmDspSessionLevel which repre-
sent ISO defined diagnostic sessions shall be used for the shortname of DcmDspSes-
sionRow:
1 DCM_DEFAULT_SESSION
2 DCM_PROGRAMMING_SESSION
3 DCM_EXTENDED_DIAGNOSTIC_SESSION
4 DCM_SAFETY_SYSTEM_DIAGNOSTIC_SESSION
c()
[SWS_Dcm_00145] dAfter all Xxx_StartProtocol() functions have returned E_OK
(meaning all components have allowed the start of the protocol), the service table is
set (see configuration parameter DcmDslProtocolSIDTable).c()

83 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00146] dAfter all Xxx_StartProtocol() functions have returned E_OK

(meaning all components have allowed the start of the protocol), the security state
is reset.c()
[SWS_Dcm_00147] dAfter all Xxx_StartProtocol() functions have returned E_OK
(meaning all components have allowed the start of the protocol), the ses-
sion state is reset to default session. Furthermore the Dcm module shall
invoke the the mode switch of the ModeDeclarationGroupPrototype DcmDiag-
nosticSessionControl by calling SchM_Switch_<bsnp>_DcmDiagnosticSessionCon-
trol(RTE_MODE_DcmDiagnosticSessionControl_DEFAULT_SESSION) .c()
Note: <bsnp> is the BSW Scheduler Name Prefix
[SWS_Dcm_00674] dIf Xxx_StartProtocol() doesn’t return E_OK, the Dcm shall return
NRC 0x22.c()

7.4.4.16.6 Protocol stop

A protocol stop can appear only in case of protocol preemption (see chapter 7.4.4.16.3
Preemption of protocol).
[SWS_Dcm_00624] dWith the reception of Dcm_TpTxConfirmation connected to
the response given by the DSL submodule, the Dcm shall not stop the current protocol
(no call to xxx_StopProtocol).c()
Note: A protocol (e.g. OBD) will be active till reset or other protocol preempts.
[SWS_Dcm_01190] dIf Xxx_StopProtocol() doesn’t return E_OK, the Dcm shall return
NRC 0x22.c()

7.4.4.17 Manage resources

Due to limited resources, the following points should be considered as hints for the
design:
• It is allowed to use and allocate only one diagnostic buffer in the Dcm module.
This buffer is then used for processing the diagnostic requests and responses.
• Output of NRC 0x78 (Response pending) responses is done with a separate
buffer.
• paged-buffer handling (see [SWS_Dcm_00028]).

84 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.4.4.18 Communication Mode Handling

Communication Mode Handling is an interface between Dcm and ComM. The ComM
informs the Dcm about the current communication state of a channel. The Dcm is calling
the ComM about active Diagnostic which shall prevent an Ecu shutdown/sleep.
The status ActiveDiagnostic shows if diagnostic requests shall keep the ECU awake
(ActiveDiagnostic ==’DCM_COMM_ACTIVE’) or if diagnostic requests shall not pre-
vent an Ecu shutdown/sleep (ActiveDiagnostic ==’DCM_COMM_NOT_ACTIVE’). Ap-
plication can change the status ActiveDiagnostic regarding to system conditions.
[SWS_Dcm_CONSTR_6027] dThe application will inform the Dcm by calling
Xxx_SetActiveDiagnostic() about the ActiveDiagnostic status.c()
[SWS_Dcm_01069] dAfter Dcm_Init, the Dcm shall set ActiveDiagnostic to
’DCM_COMM_ACTIVE’.c()
[SWS_Dcm_01070] dIf Xxx_SetActiveDiagnostic() is called with ’false’ the Dcm set
ActiveDiagnostic to ’DCM_COMM_NOT_ACTIVE’.c()
[SWS_Dcm_01071] dIf Xxx_SetActiveDiagnostic() is called with ’true’ the Dcm set Ac-
tiveDiagnostic to ’DCM_COMM_ACTIVE’.c()
[SWS_Dcm_01142] dThe Dcm shall wait the Full Communication mode indication from
the ComM (call to Dcm_ComM_FullComModeEntered) before initiating the trans-
mission of the diagnostic answer. The time to wait should be no longer than the
P2ServerMax calculated from the moment the request was received.c()
[SWS_Dcm_01143] dIf the Dcm fails to confirm a response pending transmission
(DCM_E_FORCE_RCRRP) due to [SWS_Dcm_01142], the Dcm shall trigger the Det
error DCM_E_FORCE_RCRRP_IN_SILENT_COMM.c()
Note : On the reception side a silent communication mode can lead to the lost of the
request in case of segmented transmission.

7.4.4.18.1 No Communication

The ComM module will indicate the No Communication Mode to the Dcm module by
calling Dcm_ComM_NoComModeEntered. In response, the Dcm will immediately dis-
able all transmissions (see the definition of Dcm_ComM_NoComModeEntered for de-
tails).
[SWS_Dcm_00148] dDcm_ComM_NoComModeEntered shall disable all kinds of trans-
missions (receive and transmit) of communication. This means that the message re-
ception and also the message transmission shall be off.c()
[SWS_Dcm_00149] dDcm_ComM_NoComModeEntered shall disable the Respon-
seOnEvent transmissions.c()

85 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00150] dDcm_ComM_NoComModeEntered shall disable the periodicId

transmissions (ReadDataByPeriodicIdentifier).c()
[SWS_Dcm_00151] dDcm_ComM_NoComModeEntered shall disable normal transmis-
sions.c()
[SWS_Dcm_00152] dAfter Dcm_ComM_NoComModeEntered has been called, the
Dcm module shall not call the function PduR_DcmTransmit().c()
[SWS_Dcm_01324] dIn case Dcm_ComM_NoComModeEntered is called with a Net-
workId for a ComM channel not referenced within the Dcm (see configuration parame-
ter DcmDslProtocolComMChannelRef), the Dcm shall return without performing any
further action.c()

7.4.4.18.2 Silent Communication

The ComM module will indicate the Silent Communication Mode to the Dcm module by
calling Dcm_ComM_SilentComModeEntered. In response, the Dcm will immediately
disable all transmissions (see the definition of Dcm_ComM_SilentComModeEntered
for details).
[SWS_Dcm_00153] dDcm_ComM_SilentComModeEntered shall disable all trans-
mission. This means that the message transmission shall be off.c()
[SWS_Dcm_00154] dDcm_ComM_SilentComModeEntered shall disable the Re-
sponseOnEvent transmissions.c()
[SWS_Dcm_00155] dDcm_ComM_SilentComModeEntered shall disable the period-
icId transmissions (ReadDataByPeriodicIdentifier) shall be disabled.c()
[SWS_Dcm_00156] dDcm_ComM_SilentComModeEntered shall disable the normal
transmissions.c()
[SWS_Dcm_01325] dIn case Dcm_ComM_SilentComModeEntered is called with a
NetworkId for a ComM channel not referenced within the Dcm (see configuration pa-
rameter DcmDslProtocolComMChannelRef), the Dcm shall return without perform-
ing any further action.c()

7.4.4.18.3 Full Communication

The ComM module will indicate the Full Communication Mode to the Dcm module by
calling Dcm_ComM_FullComModeEntered. In response, the Dcm will enable all trans-
missions (see the definition of Dcm_ComM_FullComModeEntered for details).
[SWS_Dcm_00157] dDcm_ComM_FullComModeEntered shall enable all kind of
communication. This means that the message reception and also the message trans-
mission shall be on.c()

86 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00159] dDcm_ComM_FullComModeEntered shall enable the Respon-

seOnEvent transmissions.c()
[SWS_Dcm_00160] dDcm_ComM_FullComModeEntered shall enable the periodicId
transmissions (ReadDataByPeriodicIdentifier).c()
[SWS_Dcm_00161] dDcm_ComM_FullComModeEntered shall enable the normal
transmissions.c()
[SWS_Dcm_00162] dAfter Dcm_ComM_FullComModeEntered has been called, the
Dcm shall handle the functions DslInternal_ResponseOnOneDataByPeriodicId() or
DslInternal_ResponseOnOneEvent() without restrictions.c()
[SWS_Dcm_01326] dIn case Dcm_ComM_FullComModeEntered is called with a Net-
workId for a ComM channel not referenced within the Dcm (see configuration parame-
ter DcmDslProtocolComMChannelRef), the Dcm shall return without performing any
further action.c()

7.4.4.18.4 Diagnostic Activation State

The Dcm notifies the ComM module about the internal diagnostic state for all networks.
There are two options for the diagnostic state on a network. In ’active’ diagnostic state,
the Dcm is processing one or more diagnostic requests from this network or the Dcm is
in a non-default session. In ’inactive’ diagnostic state, the Dcm is in default session and
is not processing a diagnostic request on that network.
When a network has no communication in progress, the Dcm will set the diagnostic ac-
tivation state to ’inactive’. When there is a diagnostic communication on a network the
Dcm sets the diagnostic state to ’active’. In any non-default session, the diagnostic state
remains in state ’active’. The communication state can also be controlled by the API
Xxx_SetActiveDiagnostic according to [SWS_Dcm_01070] and [SWS_Dcm_01071].
[SWS_Dcm_01373] dThe Dcm shall go into ’active’ diagnostic state on a network, if a
diagnostic request is received on a network or the diagnostic session is changed to
any non-default session.c(RS_Diag_04006)
[SWS_Dcm_01374] dThe Dcm shall go into ’inactive’ diagnostic state on a network
when the current diagnostic request processing is finished and the Dcm is not process-
ing a diagnostic request of another protocol on this network and if the Dcm is in default
session.c(RS_Diag_04006)
[SWS_Dcm_01375] dThe Dcm shall go into ’inactive’ diagnostic state on all networks
if a S3Server timeout occurs and the Dcm makes a transition into default session.c
(RS_Diag_04006)
[SWS_Dcm_01376] dIf ActiveDiagnostic is ’DCM_COMM_ACTIVE’ and the Dcm is do-
ing a transition into ’active’ diagnostic state of a diagnostic protocol, the Dcm shall call
ComM_DCM_ActiveDiagnostic(NetworkId), with the networkId associated to the re-
ceived Pdu (see DcmDslProtocolComMChannelRef), with every request, to inform

87 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

the ComM module about the need to stay in Full Communication Mode.c(RS_Diag_-
04006)
[SWS_Dcm_01377] dUpon a diagnostic state transition into ’inactive’, the Dcm shall
notify the ComM module about an inactive diagnostic state on a network by calling
ComM_DCM_InactiveDiagnostic(NetworkId), with the networkId associated to the re-
ceived Pdu (see DcmDslProtocolComMChannelRef).c(RS_Diag_04006)
[SWS_Dcm_01378] dThe definition of a finished diagnostic request according to
[SWS_Dcm_01374], shall be as follows:
• the Dcm has sent a positive or negative response unequal to NRC 0x78 by re-
ceiving the Dcm_TpTxConfirmation connected to the response given by the
DSL submodule
• the Dcm has processed the service with SPRMIB=true and the positive response
was suppressed
• in case of functional addressing, the Dcm has processed the service and the
negative response was suppressed.
c(RS_Diag_04006)

7.5 Diagnostic Service Dispatcher (DSD)

7.5.1 Introduction

The DSD submodule is responsible to check the validity of an incoming diagnostic re-
quest (Verification of Diagnostic Session/Security Access levels/Application permis-
sion) and keeps track of the progress of a service request execution.
[SWS_Dcm_00178] dThe DSD submodule shall only process valid requests and shall
reject invalid ones.c()

7.5.2 Use cases

The following use cases are relevant and are described in detail in the following:
• Receive a request message and transmit a positive response message
• Receive a request message and suppress a positive response
• Receive a request message and suppress a negative response
• Receive a request message and transmit a negative response message
• Send a positive response message without corresponding request
• Segmented Responses

88 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.5.2.1 Receive a request message and transmit a positive response message

This is the standard use case of normal communication ("ping-pong"). The server
receives a diagnostic request message. The DSD submodule ensures the validity of
the request message. In this use case, the request is valid and the response will be
positive. The request will be forwarded to the appropriate data processor in the DSP
submodule. When the data processor has finished all actions of data processing, it
triggers the transmission of the response message by the DSD submodule.
If the data processor processes the service immediately as part of the request indica-
tion function, the data processor can trigger the transmission inside this indication func-
tion ("synchronous"). If the processing takes a longer time (e. g. waiting on EEPROM
driver), the data processor defers some processing ("asynchronous"). The response
pending mechanism is covered by the DSL submodule. The data processor triggers
the transmission explicitly, but from within the data processor’s context.
As soon as a request message is received, the corresponding DcmPduId is blocked by
the DSL submodule (see [SWS_Dcm_00241]). During the processing of this request,
no other request of the same protocol type (e.g. an enhanced session can be ended
by a OBD session) can be received, until the corresponding response message is sent
and the DcmPduId is released again.

7.5.2.2 Receive a request message and suppress a positive response

This is a sub-use-case of the previous one. Within the UDS protocol it is possible
to suppress the positive response by setting a special bit in the request message
(see [SWS_Dcm_00200]). This special suppression handling is completely performed
within the DSD submodule.

7.5.2.3 Receive a request message and suppress a negative response

In case of functional addressing the DSD submodule shall suppress the negative re-
sponse for NRC 0x11, 0x12, 0x31, 0x7E and 0x7F (see [SWS_Dcm_00001]).

7.5.2.4 Receive a request message and transmit a negative response message

There are a many different reasons why a request message is rejected and a negative
response is to be sent. If a diagnostic request is not valid or if a request may not be
executed in the current session, the DSD submodule will reject the processing and a
negative response will be returned.
But there are even many reasons to reject the execution of a well-formed request mes-
sage, e.g. if the ECU or system state does not allow the execution. In this case, the

89 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DSP submodule will trigger a negative response including an NRC supplying additional
information why this request was rejected.
In case of a request composed of several parameters (e.g. a UDS Service Read-
DataByIdentifier (0x22) request with more than one identifier to read), each parameter
is treated separately. And each of these parameters can return an error. This kind of
request returns a positive response if at least one of the parameters was processed
successfully.
[SWS_Dcm_00827] dThe DSD sub-module shall check the received diagnostic request
in the order given by ISO14229-1 [1]. If one of the computations failed the Dcm shall
stop the execution of the NRC check sequence then stop or do not start the execution of
the received diagnostic request and finally transmit the NRC for which the computation
failed.c()

7.5.2.5 Send a positive response message without corresponding request

There are two services within the UDS protocol, where multiple responses are sent for
only one request. In general, one service is used to enable (and disable) an event- or
time-triggered transmission of another service, which again is sent by the ECU without
a corresponding request (see ISO14229-1 [1]). These services are:
• UDS Service ReadDataByPeriodicIdentifier (0x2A). This service allows the client
to request the periodic transmission of data record values from the server identi-
fied by one or more periodicDataIdentifiers.
Type 2 = UUDT message on a separate DcmTxPduId.
• ResponseOnEvent (0x86). This service requests a server to start or stop trans-
mission of responses on a specified event.
Type 1 = USDT messages on the DcmTxPduId already used for normal diagnos-
tic responses,
Type 2 = USDT messages on separate DcmTxPduId.
For Type 1, the outgoing messages must be synchronized with "normal outgoing
messages", which have a higher priority.
This handling is especially controlled by the DSL submodule. However, the DSD sub-
module also provides the possibility to generate a response without a corresponding
request.

90 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.5.2.6 Segmented Responses (paged-buffer)

Within the diagnostic protocol, some services allow to exchange a significant amount
of data, e.g. UDS Service ReadDTCInformation (0x19) and UDS Service TransferData
(0x36).
In the conventional approach, the ECU internal buffer must be large enough to keep
the longest data message which is to be exchanged (worst-case) and the complete
buffer is filled before the transmission is started.
RAM memory in an ECU often is a critical resource, especially in smaller micros. In
a more memory-saving approach, the buffer is filled only partly, transmitted partly and
then refilled partly - and so on. This paging mechanism requires only a significantly re-
duced amount of memory, but demands a well-defined reaction time for buffer refilling.
The user can decide whether to use the "linear buffer" or paged-buffer for diagnostics.

7.5.3 Interaction of the DSD with other modules

The DSD submodule is called by the DSL submodule when receiving a diagnostic mes-
sage and performs the following operations:
• delegates processing of request to the DSP submodule or external modules out-
side the Dcm
• keeps track of request processing (Return the status on <Module>_<Diagnos-
ticService>() and <Module>_<DiagnosticService>_<SubService>() APIs call or
"Service Interpreter calls")
• transmits the response of the Application to the DSL submodule (Transmit func-
tionality)

7.5.3.1 Interaction of the DSD with the DSL main functionality

Direction Explanation
Bidirectional Exchange of the Diagnostic Messages (receive/transmit).
DSD submodule to DSL Obtain latest diagnostic session and latest security level.
submodule
DSL submodule to DSD Confirmation of transmission of Diagnostic Message.
submodule

Table 7.3: Interaction between the DSD submodule and the DSL submodule

7.5.3.2 Interaction of the DSD with the DSP

91 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Direction Explanation
DSD submodule to DSP - Delegate processing of request.
submodule - Confirmation of transmission of Diagnostic Message.
DSP submodule to DSD - Signal that processing is finished.
submodule

Table 7.4: Interaction of the DSD with the DSP

7.5.4 Functional Description of the DSD

7.5.4.1 Support checking the diagnostic service identifier and adapting the di-
agnostic message

The DSD submodule shall be triggered by the DSL submodule if a new diagnostic mes-
sage is recognized. The DSD submodule will start processing by analyzing the diag-
nostic service identifier contained in the received diagnostic message.
[SWS_Dcm_00084] dIf configured (configuration parameter DcmRespondAllRe-
quest=FALSE), if the Dcm module receives a diagnostic request that contains a ser-
vice ID that is in the range from 0x40 to 0x7F or in the range from 0xC0 to 0xFF, the
Dcm shall not respond to such a request.c()
This range corresponds to the diagnostic response identifier.
[SWS_Dcm_00192] dThe DSD submodule shall analyze the (incoming) diagnostic
message for the diagnostic service identifier (based on first byte of the diagnostic
message) and shall check the supported services with the newly received diagnos-
tic service identifier.c()
[SWS_Dcm_00193] dDuring this check, the DSD submodule shall search the newly
received diagnostic service identifier in the "Service Identifier Table".c()
For performance reasons it might be necessary that the support check is done with a
"lookup table" functionality. In this "Service Identifier Table" all supported Service IDs
of the ECU are predefined.
[SWS_Dcm_00195] dThe DSL submodule shall provide the current "Service Identifier
Table"c()
Rationale for [SWS_Dcm_00195]: The "Service Identifier Table" and the information
about the supported services will be generated out of the configuration. More than one
Service Identifier Table can be configured for selection. At one time only one Service
Identifier Table can be active.
[SWS_Dcm_00196] dFor the check, the DSD submodule shall scan the active "Ser-
vice Identifier Table" for a newly received diagnostic service identifier. If this service
identifier is supported and if the configuration parameter DcmDsdSidTabFnc (see
ECUC_Dcm_00777) is not empty, the DSD submodule shall call the configured service
interface (<Module>_<DiagnosticService>). If the configuration parameter is empty,
the Dcm shall call the internally implemented service interface.c()

92 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

The diagnostic service identifier is not supported when it is not included in the "Service
Identifier Table".
[SWS_Dcm_00197] dIf the newly received diagnostic service identifier is not sup-
ported, the DSD submodule shall transmit a negative response with NRC 0x11 (Service
not supported) to the DSL submodule.c()
[SWS_Dcm_00198] dThe DSD submodule shall store the newly received diagnostic
service identifier for later use.c()
For example: WriteDataByIdentifier (for writing VIN number):
1. A new diagnostic message is received by the DSL submodule. (Diagnostic Mes-
sage WriteDataByIdentifier = 0x2E, 0xF1, 0x90, 0x57, 0x30, 0x4C, 0x30, 0x30,
0x30, 0x30, 0x34, 0x33, 0x4D, 0x42, 0x35, 0x34, 0x31, 0x33, 0x32, 0x36)
2. The DSL submodule indicates a new diagnostic message with the "Data Indica-
tion" functionality to the DSD submodule. In the diagnostic message buffer the
diagnostic message is stored (buffer = 0x2E,0xF1,0x90,..).
3. The DSD submodule executes a check of the supported services with the de-
termined service identifier (first byte of buffer 0x2E) on the incoming diagnostic
message.
4. The incoming diagnostic message is stored in the Dcm variable
Dcm_MsgContextType.
[SWS_Dcm_CONSTR_6047] dId of the Service identifier configured in DcmDsd-
SidTabServiceId shall be unique within one DcmDsdServiceTable.c()
[SWS_Dcm_00732] dFor the first call of <Module>_<DiagnosticService> the opStatus
shall be set to DCM_INITIALc()
[SWS_Dcm_00733] dThe Dcm shall not accept further requests (on same or lower
priority) while <Module>_<DiagnosticService>() returns DCM_E_PENDING. Dcm-
internal timeout handling (based on RCR-RP limitation) may lead to a cancellation
of the external diagnostic service processing.c()
[SWS_Dcm_00735] dIn case of cancellation the API <Module>_<DiagnosticService>
is called again with the parameter opStatus set to DCM_CANCELc()

7.5.4.2 Handling of "suppressPosRspMsgIndicationBit"

The "suppressPosRspMsgIndicationBit" is part of the subfunction parameter structure

(Bit 7 based on second byte of the diagnostic message, see ISO14229-1 [1] Section
6.5: Server response implementation rules).
[SWS_Dcm_00200] dIf the "suppressPosRspMsgIndicationBit" is TRUE, the DSD sub-
module shall NOT send a positive response message.c(RS_Diag_04020)

93 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00201] dThe DSD submodule shall remove the "suppressPosRspMsgIndi-

cationBit" (by masking the Bit) from the diagnostic message.c()
[SWS_Dcm_00202] dThe Dcm module shall transport the information on a suppres-
sion of a positive response being active (between the layers) via the parameter
Dcm_MsgContextType.c()
[SWS_Dcm_00203] dIn case of responsePending the Dcm module shall clear the "sup-
pressPosRspMsgIndicationBit."c()
Rationale for [SWS_Dcm_00203]: In the described case the final response (negative/-
positive) is required.
[SWS_Dcm_00204] dThe Dcm module shall only perform the "suppressPosRspMs-
gIndicationBit" handling when the configuration parameter DcmDsdSidTabSubfun-
cAvail is set for the newly received service identifierc()
Note: The "suppressPosRspMsgIndicationBit" handling needs to be considered inde-
pendent of the processing order in the request (like for RoutineControl service).
Rationale for [SWS_Dcm_00204]: The "suppressPosRspMsgIndicationBit" is only
available if a service has a subfunction.

7.5.4.3 Verification functionality

Prior of execution of a received diagnostic service, the DSD performs a set of verifica-
tions. The DSD will only accept a service, if all verifications are successfully passed.
[SWS_Dcm_01535] DSD verifications prior of service execution dThe Dcm shall
only accept a diagnostic request, if the following verifications have been passed in the
following order:c(RS_Diag_04230, RS_Diag_04005, RS_Diag_04006)
1. Verification of Manufacturer permission (Call of the manufacturer interface indi-
cation operation)
2. Verification of the SID
3. Verification of the service access control on the current authentication state
4. Verification of the Diagnostic Session
5. Verification of the Service Security Access levels
6. Verification of the Supplier permission (Call of the Supplier interface indication
operation)
7. Verification of the Mode rules for service IDs.
[SWS_Dcm_01474] dIn case the DSD generates a NRC, the Dcm shall only call
XXX_Confirmation.c(RS_Diag_04235)
This means that the Dcm will not call DspInternal_DcmConfirmation().

94 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.5.4.3.1 Verification of the diagnostic service access rights

The UDS service Authentication (0x29) is used to change the authentication state of a
diagnostic connection and to provide the access rights. Depending on the reached role
and provided white list a dynamic set of diagnostic services is available for the tester
on that connection. The DSD submodule verifies on service ID (SID) and sub-function
(SF) level, if a service can be executed or not.
[SWS_Dcm_01536] Authentication on UDS services only dThe Dcm shall only ver-
ify the authentication for UDS services. A UDS service has a service ID within the
range of 0x10 and 0xFF.c(RS_Diag_04230)
OBD services are explicitly excluded from authentication checks. By legislation the
OBD services need to be always available, independent from active authentication
state. If WWH-OBD is used the system engineer must ensure that these services are
always accessible.
[SWS_Dcm_01537] Verifying access rights dThe Dcm shall only verify and check
the configured access rights of a diagnostic service, if the container DcmDspAuthen-
tication is configured.c(RS_Diag_04230)
If no DcmDspAuthentication is configured, the Dcm will process all diagnostic services
as if the current connection would grant access to execute the current processed ser-
vice. Checking the access rights for diagnostic services is done at different levels of
the service structure. The use of diagnostic service access rights introduces means to
allow or to refuse a diagnostic service due to current roles and authentication states.
Some services shall always be allowed to be executed, like the service 0x29 (Authen-
tication) to set the current tester access rights. This service and other OEM or sup-
plier specific services should have granted access independent from the authentication
state. To realize this, the Dcm uses a default role that is used in all deauthenticated
states. In that state, all role based verifications are done as in authenticated state. The
active role is provided by the configuration.
[SWS_Dcm_01538] Access rights for services in deauthenticated state dIf the cur-
rent connection is in deauthenticated state, the Dcm shall use the role configured in
DcmDspAuthenticationDeauthenticatedRole as current role for all role based access
verification checks.c(RS_Diag_04230)
[SWS_Dcm_01539] Definition of allowed service execution dThe Dcm shall allow
the service execution, if a role verification was successful or the service is allowed by
the white list.c(RS_Diag_04233)
[SWS_Dcm_01540] Diagnostic service execution rights verification dThe Dcm
shall check if a service execution is permitted in the current authentication check or
not. The Dcm shall perform the following checks in the given order below. If a check
grants access to a service, the remaining checks are skipped:
1. Checks on service ID level
2. Checks on service ID and sub-function level

95 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

3. Checks for services with one or multiple DIDs

4. Check on dynamically defined DIDs
5. Checks on service 0x31 per sub-function
6. Checks on service 0x19 parameter MemorySelection
c(RS_Diag_04233)
[SWS_Dcm_01541] Service ID authentication check for UDS service requests
dUpon processing a diagnostic service, the Dcm shall grant access to the diagnos-
tic service if:
1. a DcmDsdServiceRole is configured for that service and the verification accord-
ing to [SWS_Dcm_01522] was successful or
2. the active white list on that connection has one entry for a SID (1-byte element)
which matches that service.
c(RS_Diag_04233)
[SWS_Dcm_01542] Service with sub-function authentication check for UDS ser-
vice requests dUpon processing a diagnostic service with sub-function, the Dcm shall
grant access to the diagnostic service if:
1. a DcmDsdSubServiceRole is configured for that service and sub-function and the
verification according to [SWS_Dcm_01522] was successful or
2. the active white list on that connection has one entry for a SID with sub-function
(2-byte element) that matches that service and sub-function.
c(RS_Diag_04230)
[SWS_Dcm_01562] White list verification for services with 3 and 4 bytes dFor 3
and 4 bytes white list for services entries, the Dcm shall verify on the full length of the
configured white list service element. The service is granted access if the first bytes of
the received request match the entire white list entry.c(RS_Diag_04233)
Verification of byte 3 and 4 within the Dsd is beyond the scope of a typical Dsd opera-
tion. It provides means to extend the capabilities of white list service verifications and
gives means to adapt to legacy authentication solutions.
[SWS_Dcm_01544] Response behavior of services without access rights dIf the
service execution verification fails due to a failed check in scope of [SWS_Dcm_01540],
the Dcm shall send a NRC 0x34 authenticationRequired and stop the service process-
ing.c(RS_Diag_04230)

7.5.4.3.2 Verification of the Diagnostic Session

The UDS Service DiagnosticSessionControl (0x10) is used to enable different diagnos-

tic sessions in the ECU (e.g. Default session, Extended session). A diagnostic session

96 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

enables a specific set of diagnostic services and/or functionality in the ECU. It further-
more enables a protocol-depending data set of timing parameters applicable to the
started session.
On receiving a service request, the DSD module will obtain the current Diagnostic
Session with Dcm_GetSesCtrlType and will verify whether the execution of the re-
quested service (NOT the UDS Service DiagnosticSessionControl (0x10)) and sub-
service is allowed in the current diagnostic session or not.
Note that the handling of the UDS Service DiagnosticSessionControl (0x10) itself is not
part of the DSD submodule.
[SWS_Dcm_00211] dIf the newly received diagnostic service is not allowed in the cur-
rent Diagnostic Session (according to the configuration parameter DcmDsdSidTab-
SessionLevelRef), the DSD submodule shall transmit a negative response with NRC
0x7F (serviceNotSupportedInActiveSession) to the DSL submodule.c()
[SWS_Dcm_00616] dIf the newly received diagnostic service is allowed in the current
Diagnostic Session ( see [SWS_Dcm_00211]), but the requested subservice is not
allowed in the current Diagnostic Session (according to the configuration parameter
DcmDsdSubServiceSessionLevelRef), the DSD submodule shall transmit a neg-
ative response with NRC 0x7E (subFunctionNotSupportedInActiveSession) to the DSL
submodule.c()

7.5.4.3.3 Verification of the Service Security Access levels

The purpose of the Security Access level handling is to provide a possibility to access
data and/or diagnostic services, which have restricted access for security, emissions, or
safety reasons. The DSD submodule shall perform this handling with the UDS Service
SecurityAccess (0x27). The DSD submodule will perform a verification whether the
execution of the requested service (NOT the UDS Service SecurityAccess (0x27)) is
allowed in the current Security level by asking for the current security level, using the
DSL function Dcm_GetSecurityLevel.
The management of the security level is not part of the DSD submodule.
Note: For some use cases (e.g. UDS Service ReadDataByIdentifier (0x22), where
some DataIdentifier can be secure) it will be necessary for the Application to call also
the function Dcm_GetSecurityLevel.
[SWS_Dcm_00217] dIf the newly received diagnostic service is not allowed in the
current Security level (according to the configuration parameter DcmDsdSidTabSe-
curityLevelRef), the DSD submodule shall transmit a negative response with NRC
0x33 (Security access denied) to the DSL submodule.c()
[SWS_Dcm_00617] dIf the newly received diagnostic service is allowed in the current
Security level ( see [SWS_Dcm_00217]), but the requested subservice is not allowed in

97 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

the current Security level (according to the configuration parameter DcmDsdSubSer-

viceSecurityLevelRef), the DSD submodule shall transmit a negative response
with NRC 0x33 (Security access denied) to the DSL submodule.c()

7.5.4.3.4 Verification of the Service mode dependencies

[SWS_Dcm_00773] dIf the newly received diagnostic service is not allowed in the
current mode condition (according to the configuration parameter DcmDsdSidTab-
ModeRuleRef), the DSD submodule shall transmit the calculated negative response
of the referenced DcmModeRule to the DSL submodule.c()
[SWS_Dcm_00774] dIf the newly received diagnostic service is allowed in the cur-
rent mode condition [SWS_Dcm_00773], but the requested subservice is not allowed
in the current mode condition (according to the configuration parameter DcmDsdSub-
ServiceModeRuleRef), the DSD submodule shall transmit the calculated negative
response of the referenced DcmModeRule to the DSL submodule.c()

7.5.4.4 Check format and subfunction support

The DSD submodule checks whether a specific subfunction is supported before exe-
cuting the requested command.
[SWS_Dcm_00273] General sub-function supported NRC check dThe DSD shall
send the negative response NRC 0x12 (sub-functionNotSupported ), if for the pro-
cessed service no configured DcmDsdSubService exists with the DcmDsdSubSer-
viceId of the processed service. This NRC check shall not be done for UDS Service
0x31 (RoutineControl).c()
The DSD submodule will check for the minimum message length before executing the
requested command.
[SWS_Dcm_00696] dThe DSD submodule shall trigger a negative response with NRC
0x13 (Incorrect message length or invalid format), if the length of the request is inferior
to the minimum length of the request.c()
[SWS_Dcm_01411] dIf DcmDsdSubService is configured for a DcmDsdService, the
Dcm shall support the sub-function configured in DcmDsdSubServiceId with SPRMIB
set to 0 or 1.c()

7.5.4.4.1 Verification of the Manufacturer Application environment/permission

The purpose of this functionality is that, just after receiving the diagnostic request, the
Manufacturer Application is requested to check permission/environment.
E.g. in after-run ECU state, it might be not allowed to process OBD requests.

98 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00218] dIf container DcmDsdServiceRequestManufacturerNoti-

fication exists, the DSD submodule shall call the operation Xxx_Indication on
all configured ServiceRequestIndication ports (see configuration parameter DcmDsd-
ServiceRequestManufacturerNotification).c()
[SWS_Dcm_00462] dIf at least a single Xxx_Indication function called according
to [SWS_Dcm_00218] returns E_REQUEST_NOT_ACCEPTED, the DSD submodule
shall give no response.c()
[SWS_Dcm_01172] dIn case of [SWS_Dcm_00462], the DSD shall only call
Xxx_Confirmation but not DspInternal_DcmConfirmation.c()
[SWS_Dcm_00463] dIf at least a single Xxx_Indication function called accord-
ing to [SWS_Dcm_00218] has returned E_NOT_OK and no function has returned
E_REQUEST_NOT_ACCEPTED, the DSD submodule shall trigger a negative re-
sponse with NRC from the ErrorCode parameter.c()
[SWS_Dcm_01321] d If more than one Xxx_Indication function called, accord-
ing to [SWS_Dcm_00218], has returned E_NOT_OK and no function has returned
E_REQUEST_NOT_ACCEPTED, the DSD submodule shall trigger a negative re-
sponse using the ErrorCode parameter from the first Xxx_Indication returning
E_NOT_OK.c(RS_Diag_04011)

7.5.4.4.2 Verification of the Supplier Application environment/permission

The purpose of this functionality is that, right before processing the diagnostic mes-
sage, the Supplier Application is requested to check permission/environment.
E.g. in after-run ECU state, it might be not allowed to process OBD requests.
[SWS_Dcm_00516] dIf container DcmDsdServiceRequestSupplierNotifica-
tion exists, the DSD submodule shall call the operation Xxx_Indication on all
configured ServiceRequestIndication ports (see configuration parameter DcmDsdSer-
viceRequestSupplierNotification).c()
[SWS_Dcm_00517] dIf at least a single Xxx_Indication function called according
to [SWS_Dcm_00516] returns E_REQUEST_NOT_ACCEPTED, the DSD submodule
shall give no response.c()
[SWS_Dcm_00518] dIf at least a single Xxx_Indication function called accord-
ing to [SWS_Dcm_00516] has returned E_NOT_OK and no function has returned
E_REQUEST_NOT_ACCEPTED, the DSD submodule shall trigger a negative re-
sponse with NRC from the ErrorCode parameter.c()
[SWS_Dcm_01322] d If more than one Xxx_Indication function called, accord-
ing to [SWS_Dcm_00516], has returned E_NOT_OK and no function has returned
E_REQUEST_NOT_ACCEPTED, the DSD submodule shall trigger a negative re-
sponse using the ErrorCode parameter from the first Xxx_Indication returning
E_NOT_OK.c(RS_Diag_04011)

99 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.5.4.5 Distribution of diagnostic message to DSP submodule

[SWS_Dcm_00221] dThe DSD submodule shall search for the executable functionality
of the DSP submodule for newly received diagnostic service identifier and shall call the
corresponding DSP service interpreter.c()

7.5.4.6 Assemble positive or negative response

[SWS_Dcm_00222] dWhen the DSP submodule has finished the execution of the re-
quested Diagnostic Service the DSD submodule shall assemble the response.c()
The execution of the DSP service interpreter can have the results:
• positive Result or
• negative Result.
Following possible Responses can be assembled:
• positive Response,
• negative Response, or
• no Response (in the case of suppression of responses).

7.5.4.6.1 Positive Response

[SWS_Dcm_00223] dThe DSD submodule shall add the response service identi-
fier and the response data stream (returned by the Application) in the parameter
"Dcm_MsgContextType".c()
[SWS_Dcm_00224] dThe DSD submodule shall therefore transfer the
Dcm_MsgContextType into a (response) buffer and shall add the service identi-
fier at the first byte of the buffer.c()
[SWS_Dcm_00225] dThe DSD submodule shall execute the "Initiate transmission"
functionality in the next execution step.c()

7.5.4.6.2 Negative Response

The DSP submodule can trigger the transmission of a negative response with a specific
NRC to the DSD submodule. For the allowed NRC of the executed Service ID please
refer to the specification of the service in ISO14229-1 [1] (see Section 4.2.4 Response
code parameter definition Table 12) and ISO15031-5 [2]. The DSP and the Application
have to take care of the correct use of NRC of the executed Service ID.

100 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00228] dThe DSD submodule shall handle all NRCs supported from the
Application and defined in Dcm_NegativeResponseCodeType.c()

7.5.4.6.3 Suppression of response

[SWS_Dcm_00231] dIn the case that the "suppressPosRspMsgIndicationBit" is in-

dicated in the functionality "Handling of suppressPosRspMsgIndicationBit" (stored in
the Variable Dcm_MsgContextType (Element: Dcm_MsgAddInfo)), the DSD submod-
ule shall activate the suppression of Positive Responses.c()
[SWS_Dcm_00001] dIn the case of a Negative Result of the execution and active
Functional Addressing the DSD submodule shall activate the suppression of the
following Negative Responses:
• NRC 0x11 (Service not supported),
• NRC 0x12 (SubFunction not supported),
• NRC 0x31 (Request out of range),
• NRC 0x7E (Subfunction not supported in active session),
• NRC 0x7F (Service not supported in active session)
c(RS_Diag_04020)

7.5.4.7 Initiate transmission

[SWS_Dcm_00232] dThe DSD submodule shall forward the diagnostic (response)

message (positive or negative response) to the DSL submodule.c()
[SWS_Dcm_00237] dThe DSL submodule shall forward the diagnostic (response)
message (positive or negative response) further to the PduR module by executing a
DSL transmit functionality.c()
The DSL submodule will receive a confirmation by the PduR module upon forwarding
the data.
[SWS_Dcm_00235] dThe DSL submodule shall forward the received confirmation from
the PduR module to the DSD submodule.c()
[SWS_Dcm_00236] dThe DSD submodule shall forward the confirmation via the inter-
nal function DspInternal_DcmConfirmation() to the DSP submodule.c()
[SWS_Dcm_00238] dIn the case that no diagnostic (response) message shall be sent
(Suppression of Responses) the DSL submodule shall not transmit any response.c()
In this case no Data Confirmation is sent from the DSL submodule to the
DSD submodule but the DSD submodule will still call internal function DspInter-
nal_DcmConfirmation().

101 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00240] dIn case the request has been fully processed by the Dcm, The
DSD submodule shall finish the processing of one Diagnostic Message of the Diagnos-
tic Service Dispatcher by calling DspInternal_DcmConfirmation().c()
Rationale for [SWS_Dcm_00240]: The DSP submodule is waiting for the execution of
the DspInternal_DcmConfirmation() functionality. So it has to be sent, also when no
Data Confirmation is provided. Altogether this means that in any of the following cases:
• Positive Response,
• Negative Response,
• Suppressed Positive Response, and
• Suppressed Negative Response
The DSD submodule will finish by calling DspInternal_DcmConfirmation() (refer to
8.10.3 DspInternal_DcmConfirmation).
[SWS_Dcm_00741] dThe DSD submodule shall call the operation Xxx_Confirmation()
on all ports using the ServiceRequestNotification interface (see configuration param-
eter DcmDsdServiceRequestManufacturerNotification and DcmDsdSer-
viceRequestSupplierNotification)c()
[SWS_Dcm_00742] dThe call of Xxx_Confirmation() shall be done right after the call
of DspInternal_DcmConfirmation()c()
[SWS_Dcm_00677] dIf the operation Indication() returns value
E_REQUEST_NOT_ACCEPTED, the Dcm module shall not send any diagnostic
response and shall end the current diagnostic request management.c()
[SWS_Dcm_00678] dIf the operation Indication() returns value E_NOT_OK, the Dcm
module shall send a negative response with NRC value equal to ErrorCode parameter
value.c()

7.6 Diagnostic Service Processing (DSP)

7.6.1 General

When receiving a function call from the DSD submodule requiring the DSP submodule
to process a diagnostic service request, the DSP always carries out following basic
process steps:
• analyze the received request message,
• check format and whether the addressed subfunction is supported,
• acquire data or execute the required function call on the DEM, SW-Cs or other
BSW modules
• assemble the response

102 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

The following sections are some general clarifications.

7.6.1.1 Check format and subfunction support

The DSP submodule will check for appropriate message length and structure before
executing the requested command.
[SWS_Dcm_00272] dThe DSP submodule shall trigger a negative response with NRC
0x13 (Incorrect message length or invalid format), when the analysis of the request
message results in formatting or length failure.c()
Note: It is up to the implementation in which detail the format check might be executed
and depends on the level of detail the diagnostic data description provides at compile
time.

7.6.1.2 Assemble response

[SWS_Dcm_00039] dThe DSP submodule shall assemble the response message ex-
cluding response service identifier and determine the response message length.c()
[SWS_Dcm_00038] dIf the paged-buffer mechanism is used, the DSP submodule shall
determine the overall response length before any data is passed to the DSD submodule
or the DSL submodule respectively.c()
Requirement [SWS_Dcm_00038] is needed because of segmented diagnostic data
transmission on CAN using ISO15765-2 [12], which requires the provision of the over-
all length of the complete data stream in the very first CAN frame of the respective
data transmission (please refer to Section 7.4.4.9 for details about the paged-buffer
mechanism).

7.6.1.3 Negative Response Codes handling

[SWS_Dcm_00271] dUnless another particular NRC is specified,the DSP submodule

shall trigger a negative response with NRC 0x10 (generalReject), when the API calls
made to execute the service do not return OK.c()
[SWS_Dcm_01414] Accepted range of Dcm_NegativeResponseCodeType for
negative responses dIf the Dcm calls an external application by any of the APIs hav-
ing the out parameter Dcm_NegativeResponseCodeType ErrorCode, the Dcm shall
accept only values in the range 0x01-0xFF in case the return value is E_NOT_OK.c()
[SWS_Dcm_01415] Behavior on application returning unexpected return code
dIf the Dcm calls an API with the out parameter Dcm_NegativeResponseCodeType
ErrorCode and the application sets this parameter to DCM_POS_RESP and E_NOT_OK
is returned, the Dcm shall report the runtime error DCM_E_INVALID_VALUE.c()

103 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00275] dThe DSP submodule shall trigger a negative response with NRC
0x31 (Request out of range), when the analysis of the request message results in other
unsupported message parameters.c()

7.6.1.4 Diagnostic mode declaration groups

[SWS_Dcm_00775] dThe Dcm shall act as a mode manager for the diagnostic modes:
1. DcmDiagnosticSessionControl (service 0x10)
2. DcmEcuReset (partly service 0x11)
3. DcmSecurityAccess (service 0x27)
4. DcmModeRapidPowerShutDown (partly service 0x11)
5. DcmCommunicationControl_<symbolic name of ComMChannelId>. (service
0x28)
6. DcmControlDTCSetting (service 0x85)
7. DcmResponseOnEvent_<RoeEventID> (service 0x86)
8. DcmAuthenticationState_<Symbolic Name of DcmDslMainConnection>
c()
Note: The RTE/SchM will prefix the names with "MODE_", wherefore the names do
not include the MODE keyword.
[SWS_Dcm_01327] dThe Dcm shall define the ModeDeclarationGroupPrototype
DcmSecurityAccess as provided-ModeGroup based on the following ModeDeclara-
tionGroup:
1 ModeDeclarationGroup DcmSecurityAccess {
2 {
3 DCM_SEC_LEV_LOCKED
4 DCM_SEC_LEV_1
5 ...
6 DCM_SEC_LEV_63
7 }
8 initialMode = DCM_SEC_LEV_LOCKED
9 };

c()
[SWS_Dcm_01328] d
1 ModeSwitchInterface SchM_Switch_<bsnp>_DcmSecurityAccess {
2 isService = true;
3 SecLevel currentMode;
4 };

c()

104 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00806] dThe Dcm shall define the ModeDeclarationGroupPrototype

DcmDiagnosticSessionControl as provided-ModeGroup based on the ModeDeclara-
tionGroup DcmDiagnosticSessionControl.c()
[SWS_Dcm_00777] dThe Dcm shall define the ModeDeclarationGroupPrototype
DcmEcuReset as provided-ModeGroup in its Basic Software Module instance based
on the ModeDeclarationGroup DcmEcuReset.c()
[SWS_Dcm_00807] dThe Dcm shall define the ModeDeclarationGroupPrototype Dcm-
ModeRapidPowerShutDown as provided-ModeGroup in its Basic Software Module in-
stance based on the ModeDeclarationGroup DcmModeRapidPowerShutDown.c()
[SWS_Dcm_00780] dThe Dcm shall define for each network which is consid-
ered in the CommunicationControl service a separate ModeDeclarationGroupProto-
type DcmCommunicationControl_<symbolic name of ComMChannelId> as provided-
ModeGroup in its Basic Software Module instance based on the ModeDeclara-
tionGroup DcmCommunicationControl.c()
[SWS_Dcm_00781] dThe Dcm shall define the ModeDeclarationGroupPrototype Dcm-
ControlDTCSetting as provided-ModeGroup in its Basic Software Module instance
based on the ModeDeclarationGroup DcmControlDTCSetting.c()
[SWS_Dcm_00933] dThe Dcm shall define for each RoeEvent a separate ModeDec-
larationGroupPrototype DcmResponseOnEvent_<Symbolic name of RoeEventId> as
provided-ModeGroup in its Basic Software Module instance based on the ModeDecla-
rationGroup DcmResponseOnEvent.c()
The Dcm provides a state machine for each RoeEvent (see Figure 7.4). The state for
a RoeEvent is needed by SWC to activate event reporting or report the Roe status to
a Did. Therefore the Dcm provides for each state of each RoeEvent a ModeDeclara-
tionGroupPrototype which reports the current state of the state machine as mode.
[SWS_Dcm_00934] dThe ModeDeclarationGroupPrototype shall represent the current
state of the ROE state machine for this RoeEvent.c()

7.6.1.5 Environmental condition dependent execution

The execution of a diagnostic service or the acceptance of certificates can be re-

stricted to a mode condition. This enables the Dcm to formalize environmental
checks. For diagnostic service processing, a further check (see [SWS_Dcm_00773]
and [SWS_Dcm_00774]) can be configured to the Dcm. This is like session and secu-
rity checks. The referenced mode rule is arbitrating on to several mode declarations of
a mode declaration groups in which the request can be processed. Otherwise a con-
figurable NRC (see [SWS_Dcm_00812]) is responded. The same mode rule checks
can be applied on certificate validation. Certificates can be restricted to certain vehicle
properties, such as VIN or a certain version number. Only if all the conditions are valid,
the certificate is accepted by the Dcm.

105 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00808] dThe DcmModeRule shall evaluate all referenced DcmModeCon-

ditions and/or nested DcmModeRules either by a logical AND in case DcmLogical-
Operator is set to DCM_AND or by a logical OR in case the DcmLogicalOperator
is set to DCM_OR. In case only a single DcmModeCondition or DcmModeRule is ref-
erenced the DcmLogicalOperator shall not be present and therefore not be used.c
()
[SWS_Dcm_CONSTR_6028] dDcmModeCondition shall either have a DcmBswMod-
eRef or a DcmSwcModeRef or a DcmSwcSRDataElementRef as external reference.c
()
[SWS_Dcm_00810] dThe DcmSwcModeRef and DcmBswModeRef of DcmModeCon-
ditions shall evaluate if the referenced Mode-Declaration is set in case of DcmCondi-
tionType is set to DCM_EQUALS or is not set in case of DcmConditionType is set
to DCM_EQUALS_NOT.c()
[SWS_Dcm_01119] Mode condition evaluation dFor each mode condition, the Dcm
shall compare a compare value with a S/R data element. The compare value is pro-
vided by DcmSwcSRDataElementValueRef or DcmModeConditionConnectionCertifi-
cateCompareElementRef and the S/R Element is by DcmSwcSRDataElementRef. The
mode condition is evaluated to true if the S/R data element value is:
• equal to the compare value in case of DcmConditionType is set to
DCM_EQUALS
• unequal to the compare value in case of DcmConditionType is set to
DCM_EQUALS_NOT
• greater than the compare value in case of DcmConditionType is set to
DCM_GREATER_THAN
• greater or equal than the compare value in case of DcmConditionType is set
to DCM_GREATER_OR_EQUAL
• less than the compare value in case of DcmConditionType is set to
DCM_LESS_THAN
• less or equal than the compare value in case of DcmConditionType is set to
DCM_LESS_OR_EQUAL.
c()
[SWS_Dcm_CONSTR_6029] dThe values DCM_GREATER_THAN,
DCM_GREATER_OR_EQUAL, DCM_LESS_OR_EQUAL and DCM_LESS_THAN
shall not used with a Mode reference (DcmBswModeRef or DcmSwcModeRef) .c()
Note: The current mode of the referenced ModeDeclarationGroupPrototypes could
be read by either the API SchM_Mode (in case of DcmBswModeRef) or by the API
Rte_Mode (in case of DcmSwcModeRef).

106 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00811] dIn case multiple DcmModeConditions are referenced within a

DcmModeRule they shall be evaluated in order of the index attributes of the EcucRef-
erenceValues for DcmArgumentRef.c()
Note: This implies the priority of NRCs
[SWS_Dcm_00782] dIf a DcmModeRule is not referenced from the DcmDspAuthen-
ticationConnection, the Dcm shall use the optional parameter DcmModeRuleN-
rcValue as NegativeResponseCode in case the mode rule is evaluated to false.c()
Mode rules for DcmDspAuthenticationConnection are not part of the NRC eval-
uation.
[SWS_Dcm_00812] dIn case a nested DcmModeRule contains also a DcmModeRu-
leNrcValue parameter, this NRC shall be used prior the higher-level NRC.c()
[SWS_Dcm_00813] dIn case DcmLogicalOperator is set to DCM_AND, the first
failed DcmModeRule with an explicit configured NRC (DcmModeRuleNrcValue) shall
be used to define the NRC for the response message.c()
[SWS_Dcm_00814] dIn case DcmLogicalOperator is set to DCM_OR, the last
failed DcmModeRule with an explicit configured NRC (DcmModeRuleNrcValue) shall
be used to define the NRC for the response message.c()
Note: The difference in the AND and OR logical operation is to allow an optimized
implementation.
[SWS_Dcm_00815] dIn case the complete evaluation result in no specific NRC the NRC
0x22 (ConditionsNotCorrect) shall be used.c()
[SWS_Dcm_00942] dThe Dcm shall create for commonly used ModeDeclara-
tionGroupPrototype of each DcmSwcModeRef of DcmModeConditions a required
mode switch port referencing this ModeDeclarationGroupPrototype. The name pattern
of this port prototype shall be DcmModeUser_<ModeDeclarationGroupPrototype>" in
case the ModeDeclarationGroupPrototype shortname is unique. Otherwise the name
pattern is implementation specific, except the required prefix "DcmModeUser_".c()
Note: ModeDeclarationGroupPrototypes are not necessarily unique, wherefore the ex-
ception is required to avoid name clashes in the Dcm Service-SWC.
Examples on using mode dependent request execution:
General assumptions:
1. DcmModeRule1 consists of DcmModeCondition1, DcmModeRule2 and Dcm-
ModeRule3
2. DcmModeRule1 defines NRC 0x22
3. DcmModeRule2 and DcmModeRule3 do not have any sub-rules
4. DcmModeRule2 defines NRC 0x72
5. DcmModeRule3 does not define a NRC value

107 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Example 1:
1) DcmModeRule1 uses an OR combination (DcmModeCondition1 OR Dcm-
ModeRule2 OR DcmModeRule3)
a) DcmModeCondition1 is failing
–> NRC 0x22 is returned
b) DcmModeRule2 is failing
–> NRC 0x72 is returned
c) DcmModeRule3 is failing
–> NRC 0x22 is returned
d) DcmModeCondition1, DcmModeRule2 and DcmModeRule3 are failing
–> NRC 0x72 is returned
e) DcmModeCondition1 and DcmModeRule3 are failing
–> NRC 0x22 is returned

Example 2:
1) DcmModeRule1 uses an AND combination (DcmModeCondition1 AND Dcm-
ModeRule2 AND DcmModeRule3)
a) DcmModeCondition1 is failing
–> NRC 0x22 is returned
b) DcmModeRule2 is failing
–> NRC 0x72 is returned
c) DcmModeRule3 is failing
–> NRC 0x22 is returned
d) DcmModeCondition1, DcmModeRule2 and DcmModeRule3 are failing
–> NRC 0x22 is returned
e) DcmModeCondition1 and DcmModeRule3 are failing
–> NRC 0x22 is returned
e) DcmModeRule2 and DcmModeRule3 are failing
–> NRC 0x72 is returned

[SWS_Dcm_CONSTR_6089] Only one compare element dIn one DcmModeCon-

dition only one of the elements DcmSwcSRDataElementRef or DcmModeCondi-
tionCertificateCompareElementRef shall be configured.c(RS_Diag_04232)
[SWS_Dcm_CONSTR_6090] Use of certificate compare elements dThe DcmMod-
eConditionCertificateCompareElementRef is only allowed, if the parent Dcm-
ModeRule is referenced from a DcmDspAuthenticationConnection.c()

7.6.1.6 Sender/Receiver Communication

[SWS_Dcm_00964] dIf DcmDspDiagnosisScaling is present, the Dcm shall de-

rive the CompuMethod from the DcmDspDiagnosisScaling container and add it
to the DataType in their respective port interface for S/R port of DataServices_Data
[SWS_Dcm_01035].c()

108 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.6.1.7 Passing SwDataDefProps properties from DEXT file to the Dcm Service
SW-C

UseCase: Pass the SwDataDefProps details like CompuMethod, DataContraints and

Units to the Dcm Service SW-C and make them there available per DID DataElement /
per RoutineControl signal. Two alternative work flows are available.

7.6.1.7.1 DcmDspDiagnosticDataElementRef workflow

Figure 7.6: DcmDspDiagnosticDataElementRef Workflow

The feature of the DcmDspDiagnosticDataElementRef workflow is the use of a

EcucForeignReference inside the generated EcuC values. While importing the DEXT
information, a dedicated EcuC parameter is generated, which holds a EcucForeign-
Reference named DcmDspDiagnosticDataElementRef to a DiagnosticDataEle-
ment in the DEXT file. This EcucForeignReference enables the access to all Sw-
DataDefProps (BaseType, CompuMethod, DataConstr, etc.) of the corresponding Di-
agnosticDataElement. The container DcmDspAlternativeDiagnosticDataEle-
ment aggregates this EcucForeignReference. In the process step of generating the
corresponding Service SWC all needed content will be copied directly based on the
EcucForeignReference from DEXT to the Service SW-C. In this work flow the existence
of the DEXT file while the generation of the Service SW-C is required.
[SWS_Dcm_CONSTR_6053] dThe aggregation of DcmDspTextTableMapping at
DcmDspAlternativeDataType is only valid if the category of the CompuMethod

109 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

of the DataType referenced by DcmDspAlternativeDataType.DcmApplicationDataType

has category set to TEXTTABLE or SCALE_LINEAR_AND_TEXTTABLE.c()

7.6.1.7.2 DcmDspAlternativeDataType.DcmApplicationDataType workflow

Figure 7.7: DcmDspAlternativeDataType.DcmApplicationDataType Workflow

The feature of the DcmDspAlternativeDataType.DcmApplicationDataType

workflow is that while importing the DEXT information beside the EcuC values also a
SW-C fragment is generated. In this SW-C fragment all needed SwDataDefProps are di-
rectly copied from the DEXT file. Inside the generated EcuC values the EcuC parame-
ter DcmDspAlternativeDataType.DcmApplicationDataType refers to the SWC
fragment and enables the access to all SwDataDefProps (BaseType, CompuMethod,
DataConstr, etc.). In the process step of generating the corresponding Service SW-C,
all needed content will be included based on the reference from DcmDspAlterna-
tiveDataType.DcmApplicationDataType to the SW-C fragment. In this work flow
the existence of the DEXT file while the generation of the Service SW-C is not required.

7.6.1.8 Asynchronous call behavior

[SWS_Dcm_01412] dIf a Dem function returns DEM_PENDING, the Dcm shall call this
function again at a later point in time as long as DEM_PENDING is returned.c()

110 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00120] dIf the number of negative responses for a requested diagnostic

tasks (see [SWS_Dcm_00024]) reaches the value defined in the configuration param-
eter DcmDslDiagRespMaxNumRespPend, the Dcm module shall stop processing the
active diagnostic request, inform the application or BSW (if this diagnostic task implies
the call to a SW-C interface or a BSW interface) by setting OpStatus parameter, of
active port interface, to DCM_CANCEL, report the runtime error DCM_E_INTERFACE_-
TIMEOUT and shall send a negative response with NRC 0x10 (General reject).c()
[SWS_Dcm_01184] dThe Dcm_SetProgConditions API shall be called again in
the next Dcm main function cycle if previous return status was E_PENDING.c()
[SWS_Dcm_00760] dThe return of DCM_E_PENDING shall do a re-triggering (e.g. in
the next MainFunction cycle).c()
[SWS_Dcm_01413] dThe return values of interfaces called with an OpStatus equal to
DCM_CANCEL shall be ignoredc()

7.6.2 UDS Services

[SWS_Dcm_00442] dThe Dcm module shall implement the services of UDS according
to Table 7.5.c()
SID Service Subfunction Supported
0x10 DiagnosticSessionControl Supported
0x11 ECUReset Supported
0x14 ClearDiagnosticInformation Supported
0x19 ReadDTCInformation Supported
0x22 ReadDataByIdentifier Supported
0x23 ReadMemoryByAddress Supported (callout)
0x24 ReadScalingDataByIdentifier Supported
0x27 SecurityAccess Supported
0x28 CommunicationControl Supported
0x29 Authentication Supported
0x2A ReadDataByPeriodicIdentifier Supported
0x2C DynamicallyDefineDataIdentifie Supported
0x2E WriteDataByIdentifier Supported
0x2F InputOutputControlByIdentifier Supported
0x31 RoutineControl Supported
0x34 RequestDownload Supported (callout)
0x35 RequestUpload Supported (callout)
0x36 TransferData Supported
0x37 RequestTransferExit Supported
0x38 RequestFileTransfer Supported (callout)
0x3D WriteMemoryByAddress Supported (callout)
0x3E TesterPresent Supported
0x83 AccessTimingParameter NRC
"ServiceNotSupported"
0x84 SecuredDataTransmission NRC
"ServiceNotSupported"
0x85 ControlDTCSetting On, off Supported

111 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

SID Service Subfunction Supported

0x86 ResponseOnEvent All excepted Supported
onComparisionOfValues
and OnTimerInterrupt
0x87 LinkControl User optional

Table 7.5: Support of UDS Services

7.6.2.1 General behavior using DEM interfaces

[SWS_Dcm_00007] dThe Dcm module shall retrieve the DTCStatusAvailabilityMask by

using the function Dem_GetDTCStatusAvailabilityMask().c()
The mask DTCStatusAvailabilityMask reflects the status bits supported by the ECU.
Note : Masking is performed in the module Dem and does not need to be done on Dcm
side (see SWS_Dem_00657 in [13]).
[SWS_Dcm_00371] dTo ensure consistent event related data during the reading se-
quence, the Dcm module shall lock the update of event related data before reading
freeze frames or extended data records. The Dcm shall lock the update using the Dem
API Dem_DisableDTCRecordUpdate(). After the locking the Dcm shall read the event
related data by calls to:
• Dem_SelectExtendedDataRecord()
• Dem_GetSizeOfExtendedDataRecordSelection()
• Dem_GetNextExtendedDataRecord()
• Dem_SelectFreezeFrameData()
• Dem_GetSizeOfFreezeFrameSelection() and
• Dem_GetNextFreezeFrameData() After the event related data is read, the Dcm
shall re-enable updates by calling Dem_EnableDTCRecordUpdate().
c()
[SWS_Dcm_00702] dIf function Dem_DisableDTCRecordUpdate() returns
DEM_PENDING, the Dcm shall retry to get the lock in the next Dcm_MainFunc-
tion.c()
[SWS_Dcm_00700] dWhen the Dcm module receives a request with the DTCStatus-
Mask set to 0x00, it shall send positive response and shall not use the Dem interface
Dem_SetDTCFilter().c()
Note: The parameter DTCFormat of the functions Dem_ClearDTC(),
Dem_SetDTCFilter(), Dem_SetFreezeFrameRecordFilter() and
Dem_GetNextFilteredDTCAndFDC() defines the output-format of the requested
DTC values for the sub-sequent API calls. For the 2-byte ISO15031-6 [14] DTC
format, the DTCFormat parameter shall be equal to DEM_DTC_FORMAT_OBD. For

112 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

the 2-byte ISO14229-1 DTC format, the DTCFormat parameter shall be equal to
DEM_DTC_FORMAT_UDS.
[SWS_Dcm_01160] dWhen the Dcm module receives a request with the DTCSeverity-
Mask set to 0x00, it shall send a positive response as specified in ISO14229-1 [1] and
shall not use the Dem interface Dem_SetDTCFilter()c()
[SWS_Dcm_00835] dThe Dcm shall call Dem_SetDTCFilter prior to
Dem_GetNumberOfFilteredDTC, any sequence of Dem_GetNextFilteredDTC,
any sequence of Dem_GetNextFilteredDTCAndFDC, as well as any sequence of
Dem_GetNextFilteredDTCAndSeverity.c()
[SWS_Dcm_00836] dThe Dcm shall call Dem_SetFreezeFrameRecordFilter prior to
any sequence of Dem_GetNextFilteredRecord.c()
[SWS_Dcm_01127] dThe Dcm module shall retrieve the DTCSeverityAvailabilityMask
by using the function Dem_GetDTCSeverityAvailabilityMask()c()
Note: The mask DTCSeverityAvailabilityMask reflects the severity bits supported by
the ECU.
[SWS_Dcm_01212] dIf Dem_DisableDTCRecordUpdate() returns
DEM_WRONG_DTC, the Dcm shall send a NRC 0x31 (RequestOutOfRange).c
()
[SWS_Dcm_01213] dIf Dem_DisableDTCRecordUpdate() returns
DEM_WRONG_DTCORIGIN, the Dcm shall send a NRC 0x31 (RequestOutOfRange).c
()
[SWS_Dcm_01234] dIf Dem_GetNextFilteredDTCAndSeverity() returns
DEM_NO_SUCH_ELEMENT and at least one matching element could be re-
trieved before, the Dcm shall send a positive response including these data elements.c
()
[SWS_Dcm_01235] dIf Dem_GetNextFilteredDTCAndSeverity() returns
DEM_NO_SUCH_ELEMENT and no matching element could be retrieved before, the
Dcm shall send a positive response only for service, subservice and mandatory data
specified in ISO 14229-1 [1].c()
[SWS_Dcm_01242] dIf Dem_GetSizeOfExtendedDataRecordSelection() returns
DEM_WRONG_DTC, DEM_WRONG_DTCORIGIN or DEM_NO_SUCH_ELEMENT,
the Dcm shall send a NRC 0x31 (RequestOutOfRange)c()
[SWS_Dcm_01250] dIf Dem_GetStatusOfDTC() returns DEM_WRONG_DTC or
DEM_WRONG_DTCORIGIN, the Dcm shall send a NRC 0x31 (RequestOutOfRange).c
()
[SWS_Dcm_01409] dIf Dem_GetStatusOfDTC() returns
DEM_NO_SUCH_ELEMENT, the Dcm shall send a positive response only for
service and subservice.c()

113 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01255] dIf Dem_SetDTCFilter() returns E_NOT_OK, the Dcm shall send

a NRC 0x31 (RequestOutOfRange).c()

7.6.2.2 Service 0x10 - Diagnostic Session Control

UDS Service 0x10 allows an external tester to enable different diagnostic sessions in
the server. A diagnostic session enables a specific set of diagnostic services and/or
functionality in the server. The service request contains the parameter:
• diagnosticSessionType
[SWS_Dcm_00250] dThe Dcm module shall implement the UDS Service 0x10.c(RS_-
Diag_04006)
[SWS_Dcm_00307] dWhen responding to UDS Service 0x10, if the requested sub-
function value is not configured in the ECU (configuration parameter DcmDspSes-
sionLevel), the DSP submodule shall trigger a negative response with NRC 0x12
(SubFunction not supported).c()
If the requested subfunction value is configured, the following steps are processed
even if the requested session type is equal to the already running session type (see
ISO14229-1 [1] Section 9.2).
[SWS_Dcm_00311] dThe send confirmation function shall set the new diagnos-
tic session type with DslInternal_SetSesCtrlType() and shall set the new timing
parameters (P2ServerMax, P2ServerMax*) (see configuration parameters DcmD-
spSessionP2ServerMax and DcmDspSessionP2StarServerMax) and do the mode
switch of the ModeDeclarationGroupPrototype DcmDiagnosticSessionControl by call-
ing SchM_Switch_<bsnp>_DcmDiagnosticSessionControl() with the new diagnostic
session type (see [SWS_Dcm_91019]).c(RS_Diag_04248)
[SWS_Dcm_00085] dThe DSP submodule shall manage internally a read ac-
cess for the dataIdentifier 0xF186 (ActiveDiagnosticSessionDataIdentifier) defined in
ISO14229-1 [1].c()

7.6.2.3 Service 0x11 - ECUReset

UDS Service ECUReset (0x11) allows an external tester to request a server reset. The
service request contains parameter:
• resetType
[SWS_Dcm_00260] dThe Dcm module shall implement the UDS Service ECUReset
(0x11).c()

114 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00373] dOn reception of a request for UDS Service 0x11 with the sub
functions other than enableRapidPowerShutDown (0x04) or disableRapidPowerShut-
Down (0x05), the Dcm module shall trigger the mode switch of ModeDeclarationGroup-
Prototype DcmEcuReset equal to the received resetType. After the mode switch is
requested the Dcm shall trigger the start of the positive response message transmis-
sion. Sub function hardReset (0x01) to HARD Sub function keyOffOnReset (0x02) to
KEYONOFF Sub function softReset (0x03) to SOFTc()
Note: By this mode switch the Dcm informs the BswM to carry out necessary actions
for the handling of this individual reset type. These actions can be configured within
the BswM action list corresponding to the requested reset type. Here the integrator can
also define if an ECU reset will finally be performed or not.
[SWS_Dcm_00594] dOn the transmit confirmation (call to Dcm_TpTxConfirma-
tion) of the positive response, the Dcm module shall trigger the mode switch
of ModeDeclarationGroupPrototype DcmEcuReset to the mode EXECUTE (via
SchM_Switch_<bsnp>_DcmEcuReset(RTE_MODE_DcmEcuReset_EXECUTE)).c()
Note: By this mode switch the Dcm requests the BswM to perform the final processing
on the reset type according to the configured action list.
[SWS_Dcm_00818] dOn reception of a request for UDS Service 0x11 with the
sub functions enableRapidPowerShutdown (0x04) or disableRapidPowerShutdown
(0x05), the Dcm module shall trigger the mode switch of ModeDeclarationGroupPro-
totype DcmRapidPowerShutDown: Sub function enableRapidPowerShutDown (0x04)
to ENABLE_RAPIDPOWERSHUTDOWN, Sub function disableRapidPowerShutDown
(0x05) to DISABLE_RAPIDPOWERSHUTDOWNc()
Note: If EnableRapidPowerShutdown is enabled, the ECU should shorten its power-
down time.
[SWS_Dcm_00589] dIn case the parameter DcmDspPowerDownTime is present, the
Dcm shall set the powerDownTime in positive response to sub-service enableRapid-
PowerShutDown with value set in DcmDspPowerDownTime.c()
[SWS_Dcm_00834] dAfter sending the positive response of EcuReset (call of
Dcm_TpTxConfirmation) the Dcm shall ignore all further requests during reset-
processing.c()
[SWS_Dcm_CONSTR_6080] DcmDspEcuResetRow container configuration dOne
container DcmDspEcuResetRow shall be configured for each DcmDsdSubService
(DcmDspEcuResetId matching to the DcmDsdSubServiceId) configured for the
UDS service ECUReset (0x11) which does not have the corresponding DcmDsdSub-
ServiceFnc parameter configured.c(RS_Diag_04098)

7.6.2.4 Service 0x14 - Clear Diagnostic Information

UDS Service ClearDiagnosticInformation (0x14) requests an ECU to clear the error

memory. The service request contains the parameter:

115 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• groupOfDTC.
[SWS_Dcm_00247] dThe Dcm module shall implement UDS Service 0x14.c()
[SWS_Dcm_01263] dUpon reception of a UDS Service ClearDiagnosticInformation
(0x14) request with parameter groupOfDTC, the Dcm module shall call the API
Dem_SelectDTC() with the following parameter values:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
• DTC: groupOfDTC from the service request
• DTCFormat: DEM_DTC_FORMAT_UDS
• DTCOrigin: DEM_DTC_ORIGIN_PRIMARY_MEMORY
c(RS_Diag_04058)
[SWS_Dcm_01400] dAfter call of Dem_SelectDTC() the Dcm shall call
Dem_GetDTCSelectionResultForClearDTC() with the following parameter value:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef.
c()
[SWS_Dcm_01265] dIn case Dem_GetDTCSelectionResultForClearDTC() returns
DEM_WRONG_DTC, the Dcm shall send a NRC 0x31 (RequestOutOfRange).c()
[SWS_Dcm_01268] dIn case Dem_GetDTCSelectionResultForClearDTC() returns
E_OK, the Dcm module shall check if application allows to clear the DTC (according
to the configuration parameter DcmDspClearDTCCheckFnc). If not, the Dcm module
shall send a negative response with NRC set to value from the parameter "ErrorCode".c
()
[SWS_Dcm_01269] dIn case application allows to clear the DTC, the Dcm module
shall check if the DTC can be cleared in the current mode condition (according to the
configuration parameter DcmDspClearDTCModeRuleRef). If not, the Dcm module
shall send the calculated negative response code of the referenced DcmModeRule.c()
[SWS_Dcm_00005] dIf the condition checks are successfully done, the Dcm module
shall call Dem_ClearDTC with the following parameter values:
• ClientId = Client Id for this Dcm instance (see DcmDemClientRef)
c(RS_Diag_04058)
[SWS_Dcm_00705] dIn case Dem_ClearDTC() returns E_OK, the Dcm module shall
send a positive response.c()
[SWS_Dcm_00707] dIn case Dem_ClearDTC() returns DEM_CLEAR_FAILED, the
Dcm shall send a negative response 0x22 (conditionsNotCorrect).c()
[SWS_Dcm_00708] dIn case Dem_ClearDTC() returns DEM_WRONG_DTC, the Dcm
shall send a negative response 0x31 (requestOutOfRange).c()

116 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00966] dIn case Dem_ClearDTC() returns DEM_CLEAR_BUSY, the Dcm

shall send a negative response 0x22 (conditionsNotCorrect).c()
[SWS_Dcm_01060] dIn case Dem_ClearDTC() returns
DEM_CLEAR_MEMORY_ERROR, the Dcm shall trigger a negative response
with NRC 0x72 (generalProgrammingFailure).c()
[SWS_Dcm_01408] dIn case Dem_ClearDTC() returns DEM_WRONG_DTCORIGIN,
the Dcm shall trigger a negative response 0x31 (requestOutOfRange).c()

7.6.2.5 Service 0x19 - Read DTC Information

Service 0x19 allows a client to read the status of server resident Diagnostic Trouble
Code (DTC) information.
[SWS_Dcm_00248] dThe Dcm module shall implement the UDS Service 0x19.c()
To setup the retrieval of specific data from the Dem module, the Dcm will
call different filter APIs (Dem_SetDTCFilter(), Dem_SetFreezeFrameRecordFilter(),
Dem_SelectFreezeFrameData() and Dem_SelectExtendedDataRecord()).
[SWS_Dcm_01043] dIn case E_NOT_OK is returned by Dem_SetDTCFilter(), the Dcm
module shall send a negative response with NRC 0x31 (requestOutOfRange).c()
[SWS_Dcm_01334] dFor all sub-functions addressing user defined fault memory,
before calling the appropriate Dem API, the Dcm shall add the value 0x0100 to
the received selection request parameter MemorySelection in order to match the
Dem_DTCOriginType.c()

7.6.2.5.1 Subfunctions 0x01, 0x07, 0x11 and 0x12

UDS Service 0x19 with subfunctions 0x01, 0x11 or 0x12 requests the ECU to report
the number of DTCs matching tester-defined criteria. The service request contains the
parameter:
• DTCStatusMask
UDS Service 0x19 with subfunction 0x07 requests the ECU to report the num-
ber of DTCs matching tester-defined criteria. The service request contains the
parameters:
• DTCSeverityMask
• DTCStatusMask
[SWS_Dcm_00376] dWhen sending a positive response to UDS Service 0x19 with sub-
function 0x01, 0x07, 0x11 or 0x12, the Dcm module shall use the data in the response
message according to Table 7.6c()

117 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Parameter name Value

DTCStatusAvailabilityMask DTCStatusAvailabilityMask (see [SWS_Dcm_00007]).
DTCFormatIdentifier Value returned by Dem_GetTranslationType()
DTCCount Value calculated according to [SWS_Dcm_00293]

Table 7.6: Subfaunction 0x01, 0x07, 0x11 and 0x12 response values

[SWS_Dcm_00293] dWhen responding to UDS Service 0x19 with subfunction

0x01, 0x07, 0x11 or 0x12, the Dcm module shall calculate the number of
DTCs using Dem_GetNumberOfFilteredDTC() after having set the DEM-filter with
Dem_SetDTCFilter() using the parameter values according to Table 7.7.c(RS_Diag_-
04058, RS_Diag_04067)
reportNumber reportNumber reportNumberOf reportNumberOf
OfDTC OfDTCBySeveri- MirrorMemory EmissionsRe-
ByStatusMask tyMaskRecord DTCByStatus- lated
Mask OBDDTCBySta-
tusMask
0x01 0x07 0x11 0x12
ClientId Client Id for this Client Id for this Client Id for this Client Id for this
Dcm instance Dcm instance Dcm instance Dcm instance
(see DcmDem- (see DcmDem- (see DcmDem- (see DcmDem-
ClientRef) ClientRef) ClientRef) ClientRef)
DTCStatusMask DTCStatusMask DTCStatusMask DTCStatusMask DTCStatusMask
from request (see from request (see from request (see from request (see
[SWS_Dcm_00700]) [SWS_Dcm_00700]) [SWS_Dcm_00700]) [SWS_Dcm_00700])
DTCFormat DEM_DTC_ DEM_DTC_ DEM_DTC_ DEM_DTC_
FORMAT_UDS FORMAT_UDS FORMAT_UDS FORMAT_UDS
DTCOrigin PRIMARY_ PRIMARY_ MIRROR_ DEM_DTC_
MEMORY MEMORY MEMORY ORIGIN_OBD_
RELEVANT_
MEMORY
FilterWithSeverity NO YES NO NO
DTCSeverityMask Not relevant DTCSeverityMask Not relevant Not relevant
from request
FilterForFaultDe- NO NO NO NO
tectionCounter

Table 7.7: Dem_SetDTCFilter() parameters values for subfunctions 0x01, 0x07, 0x11 and
0x12

7.6.2.5.2 Subfunctions 0x02, 0x0A, 0x0F, 0x13, 0x15 and 0x17

UDS Service 0x19 with subfunctions 0x02, 0x0F or 0x13 requests the DTCs (and their
associated status) that match certain conditions. The service request contains the
parameter:
• DTCStatusMask

118 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

UDS Service 0x19 with subfunction 0x0A requests all supported DTCs and their associ-
ated status. UDS Service 0x19 with subfunction 0x15 requests all DTCs with permanent
status.
[SWS_Dcm_00377] dWhen sending a positive response to UDS Service 0x19 with
subfunction 0x02, 0x0A, 0x0F, 0x13, 0x15 or 0x17, the Dcm module shall use the data
in the response message according to Table 7.8.c()
Parameter name Value
DTCStatusAvailabilityMask DTCStatusAvailabilityMask (see [SWS_Dcm_00007])
DTCAndStatusRecord As defined in [SWS_Dcm_00008] and
[SWS_Dcm_00378]
MemorySelection (subservice 0x17 From request
only)

Table 7.8: Subfunction 0x02, 0x0A, 0x0F, 0x13, 0x15 and 0x17 eesponse values

[SWS_Dcm_01545] Read user defined memory by status mask authentication

check dOn reception of the UDS Service ReadDTCInformation (0x19) with sub-
function reportUserDefMemoryDTCByStatusMask (0x17), the Dcm shall check if the
access to the selected user defined memory in parameter MemorySelection is authen-
ticated and read the DTC information only if:
• a DcmDspReadDTCInformationUserDefinedFaultMemoryRole is con-
figured with DcmDspReadDTCInformationUserDefinedFaultMemory-
RoleId matching the MemorySelection and the verification according to
[SWS_Dcm_01479] was successful or
• the active white list on that connection has for that requested user defined mem-
ory selection one entry.
c(RS_Diag_04233)
According to [SWS_Dcm_01545] the authentication checks are only executed if
DcmDspAuthentication is configured. In case of a failed authentication the NRC han-
dling is according to [SWS_Dcm_01544] and [SWS_Dcm_01551] applies.
[SWS_Dcm_00008] dOn reception of a UDS Service 0x19 request with subfunction
0x02, 0x0F and 0x13 and if the result of the bitwise AND operation between the DTC-
StatusMask received within the request message and the DTCStatusAvailabilityMask
reported by the DEM is equal to 0, the Dcm module shall answer positively with 0 DTC.c
()
[SWS_Dcm_00378] dWhen responding to UDS Service 0x19 with subfunctions 0x02,
0x0A, 0x0F, 0x13, 0x15 or 0x17, the Dcm module shall obtain the records with DTCs
(and their associated status) by repeatedly calling Dem_GetNextFilteredDTC() after
having configured the filter with Dem_SetDTCFilter() using the parameter values ac-
cording to Table 7.9.c(RS_Diag_04058, RS_Diag_04067)

119 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

reportDTC report report report report report

ByStatus Supported Mirror Emissions DTCWith UserDef
Mask DTCs Memory Related Permanent Memory
DTCBy OBDDTC Status DTCBy
StatusMask ByStatus StatusMask
Mask
0x02 0x0A 0x0F 0x13 0x15 0x17
ClientId Client Id for Client Id for Client Id for Client Id for Client Id for Client Id for
this Dcm this Dcm this Dcm this Dcm this Dcm this Dcm
instance instance instance instance instance instance
(see (see (see (see (see (see
DcmDem- DcmDem- DcmDem- DcmDem- DcmDem- DcmDem-
Clien- Clien- Clien- Clien- Clien- Clien-
tRef) tRef) tRef) tRef) tRef) tRef)
DTCStatus DTCStatus 0x00 DTCStatus DTCStatus 0x00 DTCStatus
Mask Mask from Mask from Mask from Mask from
request (see request (see request (see request (see
SWS_Dcm_ SWS_Dcm_ SWS_Dcm_ SWS_Dcm_
00700) 00700) 00700) 00700)
DTCFormat DEM_DTC_ DEM_DTC_ DEM_DTC_ DEM_DTC_ DEM_DTC_ DEM_DTC_
FOR- FOR- FOR- FOR- FOR- FOR-
MAT_UDS MAT_UDS MAT_UDS MAT_UDS MAT_UDS MAT_UDS
DTCOrigin PRIMARY_ PRIMARY_ MIRROR_ DEM_DTC_ PERMA Memory
MEMORY MEMORY MEMORY ORIGIN_ NENT_ Selection
OBD_RELE- MEMORY from request
VANT_ + 0x0100
MEMORY
FilterWith NO NO NO NO NO NO
Severity
DTCSeverity Not relevant Not relevant Not relevant Not relevant Not relevant Not relevant
Mask
FilterFor NO NO NO NO NO NO
FaultDetec-
tionCounter

Table 7.9: Dem_SetDTCFilter() parameters values for subfunctions 0x02, 0x0A, 0x0F,
0x13,0x15 and0x17

Note:
• The Dcm module can get an indication of the number of records that will be found
using Dem_GetNextFilteredDTC() by using Dem_GetNumberOfFilteredDTC().
This allows the implementation to calculate the total size of the response before
cycling through the DTCs.
• The value 0x00 used as DTCStatusMask for the subfunctions 0x0A and 0x15
disables the status byte filtering in Dem_SetDTCFilter().
[SWS_Dcm_00828] dIn case of paged buffer support is disabled, the Dcm module shall
not insert zero-padded DTCs to the response of UDS Service 0x19 with subfunctions
0x02, 0x0A, 0x0F, 0x13, 0x15 or 0x17.c()
When using paged buffer mechanism, in some case, it’s possible that the number of
DTC matching the filter change between the calculation of the total size, needed for

120 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

the first page transmission, and the sending of the further pages. For this reason, the
following requirement apply :
[SWS_Dcm_00587] dIn case of paged buffer support is enabled, The Dcm shall limit
the response size to the size calculated when sending the first page. If more DTCs
match the filter after this sending, the additional DTCs shall not be considered.c()
[SWS_Dcm_00588] dIn case of paged buffer support is enabled,The Dcm shall pad the
response with the size calculated when sending the first page. If less DTC match the
filter after this sending, the missing DTCs shall be padded with 0 value as defined in
15031-6 [14].c()
[SWS_Dcm_01229] dIf Dem_GetNextFilteredDTC() returns
DEM_NO_SUCH_ELEMENT and at least one matching element could be re-
trieved before, the Dcm shall send a positive response including these data elements.c
()
[SWS_Dcm_01230] dIf Dem_GetNextFilteredDTC() returns
DEM_NO_SUCH_ELEMENT and at no matching element could be retrieved be-
fore, the Dcm shall send a positive response only for service and subservice and
additional parameters required within a positive response.c()

7.6.2.5.3 Subfunction 0x08

UDS Service 0x19 with subfunction 0x08 requests the DTCs and the associated status
that match a tester-defined severity mask record. The service request contains the
following parameters:
• DTCSeverityMask
• DTCStatusMask
[SWS_Dcm_00379] dWhen sending a positive response to UDS Service 0x19 with sub-
function 0x08, the Dcm module shall use the data in the response message according
to Table 7.10.c()
Parameter name Value
DTCStatusAvailabilityMask DTCStatusAvailabilityMask (see [SWS_Dcm_00007])
DTCAndSeverityRecord As defined in [SWS_Dcm_00380]

Table 7.10: Subfunction 0x08 response values

[SWS_Dcm_00380] dWhen responding to UDS Service 0x19 with subfunction

0x08, the Dcm module shall obtain the DTCAndSeverityRecords by repeatedly call-
ing Dem_GetNextFilteredDTCAndSeverity() after having configured the filter with
Dem_SetDTCFilter() using the parameter values according to Table 7.11.c()
reportDTCBySeverityMaskRecord
ClientId Client Id for this Dcm instance (see DcmDemClientRef)

121 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

reportDTCBySeverityMaskRecord
DTCStatusMask DTCStatusMask from request (see [SWS_Dcm_00700]
DTCFormat DEM_DTC_FORMAT_UDS
DTCOrigin PRIMARY_MEMORY
FilterWithSeverity YES
DTCSeverityMask DTCSeverityMask from request
FilterForFaultDetectionCounter NO

Table 7.11: Dem_SetDTCFilter() parameters values for Subfunction 0x08

Note: The Dcm module can get an indication of the number of records
that will be found using Dem_GetNextFilteredDTCAndSeverity() by using
Dem_GetNumberOfFilteredDTC().

7.6.2.5.4 Subfunction 0x09

UDS Service 0x19 with subfunction 0x09 requests the severity information of a DTC.
The service request contains the parameter:
• DTCMaskRecord
[SWS_Dcm_00381] dWhen sending a positive response to UDS Service 0x19 with sub-
function 0x09, the Dcm module shall use the data in the response message according
to Table 7.12.c()
Parameter name Value
DTCStatusAvailabilityMask DTCStatusAvailabilityMask (see [SWS_Dcm_00007])
DTCAndSeverityRecord DTCSeverityMask: see [SWS_Dcm_01402]
DTCFunctionalUnit: see [SWS_Dcm_01403]
DTC: the given DTC of the request
statusOfDTC : see [SWS_Dcm_01404]

Table 7.12: Subfunction 0x09 response values

[SWS_Dcm_01402] dTo select the DTC, the Dcm module shall call the API
Dem_SelectDTC() with the following parameter values:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
• DTC: DTC from the service request
• DTCFormat: DEM_DTC_FORMAT_UDS
• DTCOrigin: DEM_DTC_ORIGIN_PRIMARY_MEMORY
c()
[SWS_Dcm_01403] dTo retrieve the DTCSeverityMask of the selected DTC, the Dcm
shall call Dem_GetSeverityOfDTC() with the following parameter value:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)

122 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

c()
[SWS_Dcm_01404] dTo retrieve the DTCFunctionalUnit of the selected DTC, the Dcm
shall call Dem_GetFunctionalUnitOfDTC() with the following parameter value:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
c()
[SWS_Dcm_01405] dTo retrieve the statusOfDTC of the selected DTC, the Dcm shall
call Dem_GetStatusOfDTC() with the following parameter value:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
c()
[SWS_Dcm_01226] dIf Dem_GetFunctionalUnitOfDTC() returns DEM_WRONG_DTC
or DEM_WRONG_DTCORIGIN, the Dcm shall send a NRC 0x31 (requestOut-
OfRange).c()
[SWS_Dcm_01240] dIf Dem_GetSeverityOfDTC() returns DEM_WRONG_DTC, the
Dcm shall send a NRC 0x31 (requestOutOfRange)c()
[SWS_Dcm_01406] dIf Dem_GetStatusOfDTC() returns DEM_WRONG_DTC or
DEM_WRONG_DTCORIGIN, the Dcm shall send a NRC 0x31 (requestOutOfRange).c
()

7.6.2.5.5 Subfunctions 0x06/0x10/0x19

The UDS Service 0x19 with subfunction 0x06, 0x10 or 0x19 requests a specific Ex-
tended Data Records for a specific DTC. The service request contains the parameters:
• DTCMaskRecord
• DTCExtendedDataRecordNumber
[SWS_Dcm_01547] Read user defined memory extended data record authentica-
tion check dOn reception of the UDS Service ReadDTCInformation (0x19) with sub-
function reportUserDefMemoryDTCExtDataRecordByDTCNumber (0x19), the Dcm
shall check if the access to the selected user defined memory in parameter Memo-
rySelection is authenticated and read the DTC information only if:
• a DcmDspReadDTCInformationUserDefinedFaultMemoryRole is configured
with DcmDspReadDTCInformationUserDefinedFaultMemoryRoleId matching the
MemorySelection and the verification according to [SWS_Dcm_01522] was suc-
cessful or
• the active white list on that connection has for that requested user defined mem-
ory selection one entry.
c(RS_Diag_04233)

123 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

According to [SWS_Dcm_01537] the authentication checks are only executed if

DcmDspAuthentication is configured. In case of a failed authentication the NRC han-
dling is according to [SWS_Dcm_01485] and [SWS_Dcm_01544] applies.
[SWS_Dcm_00386] dUpon reception of UDS Service 0x019 with subfunction 0x06 or
0x10 or 0x19, the Dcm shall retrieve from the Dem the stored extended data records for
the requested DTC and origin.c()
[SWS_Dcm_00295] dWhen responding to UDS Service 0x19 with subfunction 0x06,
0x10 or 0x19, the Dcm module shall calculate the statusOfDTC by first calling
Dem_SelectDTC() with the parameters values set according to Table 7.13 and then
Dem_GetStatusOfDTC() with ClientId = Client Id for this Dcm instance (see DcmDem-
ClientRef).c(RS_Diag_04058)
reportDTC report reportUserDef
ExtendedData MirrorMemoryDTC MemoryDTC
Record ExtendedData ExtDataRecord
ByDTCNumber Record ByDTCNumber
ByDTCNumber
0x06 0x10 0x19
ClientId Client Id for this Dcm Client Id for this Dcm Client Id for this Dcm
instance (see instance (see instance (see
DcmDemClientRef) DcmDemClientRef) DcmDemClientRef)
DTC DTCMaskRecord from DTCMaskRecord from DTCMaskRecord from
request request request
DTCOrigin PRIMARY_MEMORY MIRROR_MEMORY MemorySelection
from request +
0x0100

Table 7.13: Dem_SelectDTC() parameters values for subfunctions 0x06, 0x10 and 0x19

[SWS_Dcm_00841] dIf Dem_GetNextExtendedDataRecord() returns E_OK and Buf-

Size 0 (empty buffer), the Dcm module shall omit the DTCExtendedDataRecordNumber
for the related record in the response of service 0x19 0x06/0x10/0x19.c()
[SWS_Dcm_00382] dWhen responding to UDS Service 0x19 with subfunction 0x06,
0x10 or 0x19, the Dcm module shall calculate the DTCExtendedDataRecord by first
calling Dem_SelectExtendedDataRecord() with the parameter values set according
to Table 7.14 and then call Dem_GetNextExtendedDataRecord() repeatedly until
DEM_NO_SUCH_ELEMENT is returned.c()
reportDTCExtended- reportMirrorMemoryDTCreportUserDefMemory
DataRecord Extended- DTCExtDataRecord
ByDTCNumber DataRecord ByDTCNumber
ByDTCNumber
0x06 0x10 0x19
ClientId Client Id for this Dcm Client Id for this Dcm Client Id for this Dcm
instance (see instance (see instance (see
DcmDemClientRef) DcmDemClientRef) DcmDemClientRef)
DTC DTCMaskRecord from DTCMaskRecord from DTCMaskRecord from
request request request

124 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DTCOrigin PRIMARY_MEMORY MIRROR_MEMORY Memory Selection

from request +
0x0100
ExtendedDataNumber DTCExtendedData DTCExtendedData DTCExtendedData
RecordNumber from RecordNumber from RecordNumber from
request request request

Table 7.14: Dem_SelectExtendedDataRecord() parameters values for subfunctions 0x06,

0x10 and 0x19

As required in [SWS_Dcm_00371], the Dcm module shall obtain the size of the ex-
tended data record by using Dem_GetSizeOfExtendedDataRecordSelection().

7.6.2.5.6 Subfunction 0x03

UDS Service 0x19 with subfunction 0x03 allows an external tester to request the corre-
sponding DTCs for all FreezeFrame records present in an ECU.
[SWS_Dcm_00300] dWhen sending a positive response to UDS Service 0x19 with sub-
function 0x03, the Dcm module shall use the data in the response message according
to Table 7.15.c()
Parameter name Value
DTCRecord / DTCSnapshotRecord- As defined in [SWS_Dcm_00299]
Number

Table 7.15: Subfunction 0x03 response values

125 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Figure 7.8: Request DTC Snapshot Record Identification

[SWS_Dcm_00298] dWhen UDS Service 0x19 with subfunction 0x03 is re-

quested,the DSP submodule shall retrieve the number of stored freeze frame
records by calling Dem_SetFreezeFrameRecordFilter() with DTCFormat equal to
DEM_DTC_FORMAT_UDS and Dem_GetNumberOfFreezeFrameRecords.c()
[SWS_Dcm_00299] dWhen responding to UDS Service 0x19 with subfunction 0x03,
the Dcm module shall obtain the consecutive DTCs and DTCSnapshotRecordNumbers
by repeatedly calling Dem_GetNextFilteredRecord().c()
When using paged buffer mechanism, in some case, it’s possible that the number of
DTC matching the filter change between the calculation of the total size, needed for
the first page transmission, and the sending of the further pages. For this reason, the
requirement [SWS_Dcm_00587] and [SWS_Dcm_00588] shall be considered for the
implementation of this subservice.
[SWS_Dcm_01237] dIf Dem_GetNextFilteredRecord() returns
DEM_NO_SUCH_ELEMENT and at least one matching element could be re-
trieved before, the Dcm shall send a positive response including these data elements.c
()
[SWS_Dcm_01238] dIf Dem_GetNextFilteredRecord() returns
DEM_NO_SUCH_ELEMENT and no matching element could be retrieved be-
fore, the Dcm shall send a positive response only for service and subservice.c
()
[SWS_Dcm_01256] dIf Dem_SetFreezeFrameRecordFilter() returns E_NOT_OK, the
Dcm shall send a NRC 0x31 (RequestOutOfRange).c()

126 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.6.2.5.7 Subfunctions 0x04 and 0x18

Using UDS Service 0x19 with subfunction 0x04 or 0x18, an external tester can request
FreezeFrame information for one or all FreezeFrames of a specific DTC. The service
request contains parameters:
• DTCMaskRecord
• DTCSnapshotRecordNumber
The subfunction 0x18 has an additional MemorySelection.

Figure 7.9: Request DTC Snapshot Record by Snapshot Record Number

[SWS_Dcm_01546] Read user defined memory snapshot record authentication

check dOn reception of the UDS Service ReadDTCInformation (0x19) with sub-
function reportUserDefMemoryDTCSnapshotRecordByDTCNumber (0x18), the Dcm
shall check if the access to the selected user defined memory in parameter MemoryS-
election is authenticated and read the DTC information only if:
• a DcmDspReadDTCInformationUserDefinedFaultMemoryRole is configured
with DcmDspReadDTCInformationUserDefinedFaultMemoryRoleId matching the
MemorySelection and the verification according to [SWS_Dcm_01522] was suc-
cessful or
• the active white list on that connection has for that requested user defined mem-
ory selection one entry.
c(RS_Diag_04233)

127 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

According to [SWS_Dcm_01546] the authentication checks are only executed if

DcmDspAuthentication is configured. In case of a failed authentication the NRC han-
dling is according to [SWS_Dcm_01485] and [SWS_Dcm_01551] applies.
[SWS_Dcm_00302] dWhen sending a positive response to UDS Service 0x19 with
subfunction 0x04 or 0x18, the Dcm module shall use the data in the response message
according to Table 7.16.c()
Parameter name Value in Subservice 0x04 Value in Subservice 0x18
DTCAndStatusRecord DTC from the request, DTC from the request,
statusOfDTC according to statusOfDTC according to
[SWS_Dcm_00383] [SWS_Dcm_01147]
DTCSnapshotRecordNum- The DTCSnapshotRecord The DTCSnapshotRecord
ber Number is contained in the Number is contained in the
output buffer from the Dem_ output buffer from the Dem_
GetNextFreezeFrame() call. GetNextFreezeFrame() call.
see [SWS_Dcm_00384] see [SWS_Dcm_00384].
DTCSnapshotRecordNum- As defined in As defined in
berOfIdentifiers / DTCSnap- [SWS_Dcm_00384] [SWS_Dcm_00384]
shotRecord
MemorySelection n/a From request

Table 7.16: Subfunction 0x04 and 0x18 response values

[SWS_Dcm_00383] dWhen responding to UDS Service 0x19 with subfunction 0x04,

the Dcm module shall obtain the status of the DTC by first calling Dem_SelectDTC()
with the following parameters:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
• DTC: DTC from the request
• DTCOrigin: DEM_DTC_ORIGIN_PRIMARY_MEMORY
and then Dem_GetStatusOfDTC() with ClientId = Client Id for this Dcm instance (see
DcmDemClientRef)c(RS_Diag_04058)
[SWS_Dcm_01147] dWhen responding to UDS Service 0x19 with subfunction 0x18,
the Dcm module shall obtain the status of the DTC by first calling Dem_SelectDTC()
with the following parameters:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef
• DTC: DTC from the request
• DTCOrigin: Memory Selection from request + 0x0100
and then Dem_GetStatusOfDTC() with ClientId = DcmDemClientRefc(RS_Diag_-
04058)
[SWS_Dcm_00384] dUpon reception of UDS Service 0x019 with subfunction 0x04 or
0x18, the Dcm shall retrieve from the Dem the stored snapshot records for the requested
DTC and origin.c(RS_Diag_04058)

128 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00441] dThe Dcm module shall obtain the size of the

data returned by Dem in Dem_GetNextFreezeFrameData() call by using
Dem_GetSizeOfFreezeFrameSelection().c()
To get the size of all FreezeFrame data, the Dcm module calls
Dem_SelectFreezeFrameData() with RecordNumber set to 0xFF.
[SWS_Dcm_01220] dIf Dem_GetNextFreezeFrameData() returns
DEM_WRONG_DTC or DEM_WRONG_DTCORIGIN the Dcm shall send a NRC
0x31 (RequestOutOfRange)c()
[SWS_Dcm_01430] dWhen responding to UDS Service 0x19 with subfunction
0x04, or 0x18, the Dcm shall collect the freeze frame data by first calling
Dem_SelectFreezeFrameData() and then call Dem_GetNextFreezeFrameData() re-
peatedly until DEM_NO_SUCH_ELEMENT is returned.c()
[SWS_Dcm_01224] dIf at least one of the requested freeze frame data is supported,
the Dcm shall send a positive response. Otherwise the Dcm shall send a NRC 0x31
(RequestOutOfRange).c()
[SWS_Dcm_01246] dIf Dem_GetSizeOfFreezeFrameSelection() returns
DEM_WRONG_DTC, DEM_WRONG_DTCORIGIN or DEM_NO_SUCH_ELEMENT
the Dcm shall send a NRC 0x31 (RequestOutOfRange).c()

7.6.2.5.8 Subfunction 0x05

UDS Service 0x19 with subfunction 0x05 allows an external tester to request Freeze-
Frame information for a specific FreezeFrame record number. The service request
contains parameter:
• DTCStoredDataRecordNumber
Due to Dem limitation, the diagnostic service $19 05 is limited to the OBD legislative
freeze frame.
[SWS_Dcm_00632] dOn reception of service 0x19 with subfunction 0x05, if the record
number of the diagnostic request is different from 0x00, the Dcm module shall send a
negative response with NRC 0x31 (request out of range).c()
[SWS_Dcm_00574] dWhen sending a positive response to UDS Service 0x19 with
subfunction 0x05 and DTCStoredDataRecordNumber is 0x00, the Dcm module shall
use the data in the response message according to Table 7.17.c()
Parameter name Value
DTCStoredDataRecordNumber DTCStoredDataRecordNumber from request (0x00)
DTCAndStatusRecord DTC according to [SWS_Dcm_01193], statusOfDTC
according to [SWS_Dcm_00389]
DTCStoredDataRecordNumberOfIden- As defined in [SWS_Dcm_00388]
tifiers / DTCStoredDataRecord

Table 7.17: Subfunction 0x05 response values

129 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00388] dWhen responding to UDS Service 0x19 with subfunction 0x05

and DTCStoredDataRecordNumber is 0x00, the Dcm shall compose the OBD Freeze-
frame by looping all DcmDspPid and collecting all DcmDspPidData which are con-
figured for service 0x02 by calling Dem_DcmReadDataOfOBDFreezeFrame() for the
Data Element. The Dcm shall compose the DidId by adding 0xF400 to the Pid, and
calculate padding and supported informations.c(RS_Diag_04058)
[SWS_Dcm_01193] dWhen responding to UDS Service 0x19 with subfunc-
tion 0x05 and DTCStoredDataRecordNumber is 0x00, the Dcm shall call
Dem_DcmGetDTCOfOBDFreezeFrame() with FrameNumber 0x00 and DTCFormat
DEM_DTC_FORMAT_UDS to retrieve the DTC of the provided FreezeFrame.c()
[SWS_Dcm_00389] dWhen responding to UDS Service 0x19 with subfunction 0x05
and DTCStoredDataRecordNumber is 0x00, the Dcm module shall obtain the status of
the DTC by first calling Dem_SelectDTC() with the following parameters:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
• DTC: DTC as defined in [SWS_Dcm_00388]
• DTCOrigin: DEM_DTC_ORIGIN_PRIMARY_MEMORY
and then Dem_GetStatusOfDTC() with the following parameter:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
c(RS_Diag_04058)

7.6.2.5.9 Subfunctions 0x0B, 0x0C, 0x0D and 0x0E

An external test tool can request the first occurred or most recent failed or confirmed
DTC and associated status, by sending the UDS Service request 0x19 including one of
the following sub-functions 0x0B, 0x0C, 0x0D, 0x0E
[SWS_Dcm_00392] dWhen sending a positive response to UDS Service 0x19 with sub-
function 0x0B, 0x0C, 0x0D or 0x0E, the Dcm module shall use the data in the response
message according to Table 7.18.c()
Parameter name Value
DTCStatusAvailabilityMask DTCStatusAvailabilityMask (see [SWS_Dcm_00007])
DTCAndStatusRecord The DTC is obtained according to [SWS_Dcm_00466], the
StatusOfDtc is obtained according to [SWS_Dcm_00393]

Table 7.18: Subfunctions 0x0B, 0x0C, 0x0D and 0x0E response values

[SWS_Dcm_00393] dFor the purpose of responding to UDS Service 0x19 with sub-
functions 0x0B, 0x0C, 0x0D or 0x0E, the Dcm module shall obtain the StatusOfDtc by
calling Dem_GetStatusOfDTC() with the following parameter values:
• ClientId :Client Id for this Dcm instance (see DcmDemClientRef

130 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• DTC: the DTC value as defined in [SWS_Dcm_00466]

• DTCOrigin: DEM_DTC_ORIGIN_PRIMARY_MEMORY
c(RS_Diag_04058)
[SWS_Dcm_00466] dFor the purpose of responding to UDS Service 0x19 with
subfunctions 0x0B, 0x0C, 0x0D or 0x0E, the Dcm shall obtain the DTC with
Dem_GetDTCByOccurrenceTime() using the parameter values according to Table
7.19.c()
reportFirstTest reportFirst reportMost reportMost
FailedDTC ConfirmedDTC RecentTest Recent
FailedDTC ConfirmedDTC
0x0B 0x0C 0x0D 0x0E
ClientId Client Id for this Client Id for this Client Id for this Client Id for this
Dcm instance Dcm instance Dcm instance Dcm instance
(see DcmDem- (see DcmDem- (see DcmDem- (see DcmDem-
ClientRef) ClientRef) ClientRef) ClientRef)
DTCRequest DEM_FIRST_ DEM_FIRST_ DEM_MOST_ DEM_MOST_
FAILED_DTC DET_ RECENT_ REC_DET_
CONFIRMED_ FAILED_DTC CONFIRMED_
DTC DTC

Table 7.19: Dem_GetDTCByOccurrenceTime() parameters values for subfunctions 0x0B,

0x0C, 0x0D and 0x0E

[SWS_Dcm_00766] dIf the Dcm received DEM_NO_SUCH_ELEMENT by calling

Dem_GetDTCByOccurrenceTime it shall reply with a positive response and empty DT-
CAndStatusRecord.c()

7.6.2.5.10 Subfunction 0x14

An external test tool may request an ECU to report the FaultDetectionCounter for all
DTCs with a "Prefailed" status, by sending a UDS Service request 0x19 with subfunction
0x14.
[SWS_Dcm_00464] dWhen sending a positive response to UDS Service 0x19 with sub-
function 0x14, the Dcm module shall use the data in the response message according
to Table 7.20.c()
Parameter name Value
DTC The DTC is obtained according from the call to
Dem_GetNextFilteredDTCAndFDC()
DTCFaultDetectionCounter The DTCFaultDetectionCounter is obtained according
from the call to Dem_GetNextFilteredDTCAndFDC()

Table 7.20: Subfunction 0x14 response values

131 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00465] dWhen responding to UDS Service 0x19 with subfunctions 0x14,

the Dcm module shall obtain the DTCFaultCounter of every DTCs with status "prefailed"
by repeatedly calling Dem_GetNextFilteredDTCAndFDC() after having configured the
filter with Dem_SetDTCFilter() using the parameter values according to Table 7.21.c
(RS_Diag_04058)
Parameter name Value
ClientId Client Id for this Dcm instance (see DcmDemClientRef)
DTCStatusMask 0x00
DTCFormat DEM_DTC_FORMAT_UDS
DTCOrigin PRIMARY_MEMORY
FilterWithSeverity NO
DTCSeverityMask Not relevant
FilterForFaultDetectionCounter YES

Table 7.21: Dem_GetNextFilteredDTCAndFDC() parameters values for subfunctions 0x14

[SWS_Dcm_00681] dThe Dcm module shall obtain the number of records

that will be found using Dem_GetNextFilteredDTCAndFDC() by using
Dem_GetNumberOfFilteredDTC().c()
[SWS_Dcm_00519] dThe calls to Dem_SetDTCFilter() with parameter FilterForFault-
DetectionCounter set to YES shall be done in the context of the Dcm_MainFunctionc
()
This allows the implementation to calculate the total size of the response before cycling
through the DTCs.
When using paged buffer mechanism, in some case, it’s possible that the number of
DTC matching the filter change between the calculation of the total size, needed for
the first page transmission, and the sending of the further pages. For this reason, the
requirement [SWS_Dcm_00587] and [SWS_Dcm_00588] shall be considered for the
implementation of this subservice.
[SWS_Dcm_01232] dIf Dem_GetNextFilteredDTCAndFDC() returns
DEM_NO_SUCH_ELEMENT and at least one matching element could be re-
trieved before, the Dcm shall send a positive response including these data elements.c
()
[SWS_Dcm_01233] dIf Dem_GetNextFilteredDTCAndFDC() returns
DEM_NO_SUCH_ELEMENT and no matching element could be retrieved be-
fore, the Dcm shall send a positive response only for service and subservice.c
()

7.6.2.5.11 Subfunction 0x42

UDS Service 0x19 with subfunction 0x42 requests WWH OBD DTCs matching a DTC
status mask a severity mask record. The service request contains the following pa-
rameters:

132 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• FunctionalGroupIdentifier
• DTCSeverityMask
• DTCStatusMask
[SWS_Dcm_01128] dThe Dcm shall reject request messages for subFunction 0x42
with FunctionalGroupIdentifier unequal to 0x33 by returning NRC 0x31 (requestOut-
OfRange)c()
[SWS_Dcm_01129] dWhen sending a positive response to UDS Service 0x19 with sub-
function 0x42, the Dcm module shall use the data in the response message according
to Table 7.22.c()
Parameter name Value
FunctionalGroupIdentifier 0x33
DTCStatusAvailabilityMask Dem_GetDTCStatusAvailabilityMask (see
[SWS_Dcm_00007] )
DTCSeverityAvailabilityMask Dem_GetDTCSeverityAvailabilityMask (see
[SWS_Dcm_01127])
DTCFormatIdentifier Dem_GetTranslationType (limited to values 0x04 and
0x02)
DTCAndSeverityRecord As defined in [SWS_Dcm_01130]

Table 7.22: Subfunction 0x42 response values

[SWS_Dcm_01130] dWhen responding to UDS Service 0x19 with subfunction

0x42, the Dcm module shall obtain the DTCAndSeverityRecords by repeatedly call-
ing Dem_GetNextFilteredDTCAndSeverity() after having configured the filter with
Dem_SetDTCFilter() using the parameter values according to Table 7.23.c()
Parameter name Value
ClientId Client Id for this Dcm instance (see DcmDemClientRef)
DTCStatusMask DTCStatusMask from request (see [SWS_Dcm_00700])
DTCFormat DEM_DTC_FORMAT_UDS
DTCOrigin DEM_DTC_ORIGIN_OBD_RELEVANT_MEMORY
FilterWithSeverity YES
DTCSeverityMask DTCSeverityMask from request
FilterForFaultDetectionCounter NO

Table 7.23: Dem_GetNextFilteredDTCAndSeverity() parameters values for subfunctions

0x42

[SWS_Dcm_01131] dThe return values of Dem_GetNextFilteredDTCAndSeverity shall

be filled according to Table 7.24.c()
Parameter name Value
DTCSeverity DTCSeverity
DTCHighByte (MSB) DTC (high byte)
DTCMiddleByte DTC (middle byte)
DTCLowByte DTC (low byte)
statusOfDTC DTCStatus

133 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Parameter name Value

Table 7.24: Dem_GetNextFilteredDTCAndSeverity return values

Note: The Dcm module can get an indication of the number of records
that will be found using Dem_GetNextFilteredDTCAndSeverity() by using
Dem_GetNumberOfFilteredDTC().

7.6.2.5.12 Subfunction 0x55

With UDS Service 0x19 with sub-function 0x55 a client can retrieve a list of WWH-OBD
DTCs with the "permanent DTC" status. The service request contains the following
parameter:
• FunctionalGroupIdentifier
[SWS_Dcm_01343] dThe Dcm shall only process request messages for sub-function
0x55 with FunctionalGroupIdentifier equal to 0x33.c()
[SWS_Dcm_01344] dThe Dcm shall reject request messages for sub-function 0x55
with FunctionalGroupIdentifier unequal to 0x33 by returning NRC 0x31 (RequestOut-
OfRange).c()
[SWS_Dcm_01345] dWhen sending a positive response to UDS Service 0x19 with sub-
function 0x55, the Dcm module shall use the following data in the response message
according to Table 7.25.c()
Parameter name Value
FunctionalGroupIdentifier 0x33
DTCStatusAvailabilityMask Dem_GetDTCStatusAvailabilityMask (see
[SWS_Dcm_00007] )
DTCFormatIdentifier Dem_GetTranslationType (limited to values 0x04 and
0x02)
DTCAndStatusRecord As returned by Dem_GetNextFilteredDTC()

Table 7.25: Subfunction 0x55 response values

Note : When responding to UDS Service 0x19 with sub-function 0x55, the
Dcm module could obtain the DTCAndStatusRecords by repeatedly calling
Dem_GetNextFilteredDTC() after having configured the filter with Dem_SetDTCFilter()
using the parameter values according to Table 7.26.
Parameter name Value
ClientId See DcmDemClientRef
DTCStatusMask 0x00
DTCFormat DEM_DTC_FORMAT_UDS
DTCOrigin DEM_DTC_ORIGIN_PERMANENT_MEMORY
FilterWithSeverity NO
DTCSeverityMask Not relevant
FilterForFaultDetectionCounter NO

134 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Parameter name Value

Table 7.26: Dem_GetNextFilteredDTCAndSeverity() parameters values for subfunctions

0x42

The Dcm module can get an indication of the number of records that will be found using
Dem_GetNextFilteredDTC() by using Dem_GetNumberOfFilteredDTC().
[SWS_Dcm_01346] dWhen responding to UDS Service 0x19 with sub-function
0x55 and Dem_GetTranslationType returns a Dem_DTCTranslationFormatType
different to 0x02 (DEM_DTC_TRANSLATION_SAEJ1939_73) or 0x04
(DEM_DTC_TRANSLATION_J2012DA_FORMAT_04), the Dcm module shall re-
turn NRC 0x10 (generalReject).c()

7.6.2.6 Service 0x22 - ReadDataByIdentifier

[SWS_Dcm_00253] dThe Dcm module shall implement the UDS Service ReadDataByI-
dentifier (0x22)c()
[SWS_Dcm_01335] dOn reception of the UDS Service ReadDataByIdentifier (0x22), if
the number of requested DID exceeds the configured maximum number of data identi-
fiers (refer to configuration parameter DcmDspMaxDidToRead), the Dcm module shall
send NRC 0x13 (Incorrect message length or invalid format)c()
With UDS Service 0x22, the tester can request the value of one or more DIDs.
[SWS_Dcm_01548] Read UDS DID authentication check dOn reception of the UDS
Service ReadDataByIdentifier (0x22), the Dcm shall check if the access to all requested
DIDs outside the range 0xF200-0xF8FF is authenticated and read the data identifiers
only if:
• a DcmDspDidReadRole is configured for that DID and the verification according
to [SWS_Dcm_01522] was successful or
• the active white list on that connection has for each requested DID one entry with
read access that matches that DID.
c(RS_Diag_04233)
[SWS_Dcm_01549] Read Dynamically defined DID authentication check dOn re-
ception of the UDS Service ReadDataByIdentifier (0x22), the Dcm shall check for all
requested DIDs inside the range 0xF200-0xF3FF if the content is based of DIDs or
parts of DIDs that are authenticated and read the data identifiers only if:
• a DcmDspDidReadRole is configured for those DIDs and the verification accord-
ing to [SWS_Dcm_01522] was successful or
• the active white list on that connection has for each requested DID one entry with
read access that matches those DIDs.

135 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

c(RS_Diag_04233)
According to [SWS_Dcm_01537] the authentication checks are only executed if
DcmDspAuthentication is configured. In case of a failed authentication the NRC han-
dling is according to [SWS_Dcm_01544] and [SWS_Dcm_01551] applies.
[SWS_Dcm_00438] dOn reception of the UDS Service ReadDataByIdentifier (0x22)
, for every requested DID the Dcm module shall check if the DID is supported (see
configuration parameter DcmDspDid and DcmDspDidRange) If none of the requested
DIDs is supported, the Dcm module shall send NRC 0x31 (Request out of range).c()
[SWS_Dcm_00651] dOn reception of the UDS Service ReadDataByIdentifier (0x22)
with DID in the range 0xF200 to 0xF3FF, the Dcm module shall check if the DID can be
dynamically defined (the DcmDspDidInfo it references has the DcmDspDidDynami-
callyDefined set to true). If yes, if this DID has not been dynamically defined yet by
calls to the DynamicallyDefineDataIdentifier (0x2C) service, i.e. it has no data sources
defined, the Dcm module shall send NRC 0x31 (Requestout of range)c()
[SWS_Dcm_00652] dOn reception of the UDS Service ReadDataByIdentifier (0x22)
with DID in the range 0xF200 to 0xF3FF, if verification has been successfully done (see
[SWS_Dcm_00651]) and the dynamic DID has been defined with a DID source (see
[SWS_Dcm_00646]), the Dcm module shall use the configuration of this DID source to
read the data.c()
[SWS_Dcm_00864] dOn reception of the UDS Service ReadDataByIdentifier (0x22)
with DID in the range 0xF200 to 0xF3FF, if verification has been successfully done
(see [SWS_Dcm_00651]) and the dynamic DID has been defined with a DID source
(see [SWS_Dcm_00646]), the Dcm module shall do the session, security and mode
dependencies checks for all source DIDs in case the configuration parameter DcmD-
spDDDIDcheckPerSourceDID is set to TRUE.c()
[SWS_Dcm_00865] dIn case the configuration parameter DcmDspDDDIDcheckPer-
SourceDID is set to FALSE, there is no session, security or mode dependencies check
for the source DIDs.c()
Note: In case there is a need to validate the session or security dependencies always,
the DDDID should be cleared by any security and session transitions.
[SWS_Dcm_00653] dOn reception of the UDS Service ReadDataByIdentifier (0x22)
with DID in the range 0xF200 to 0xF3FF, if verification has been successfully done (see
[SWS_Dcm_00651]) and the dynamic DID has been defined with a memory address
(see [SWS_Dcm_00646]), the Dcm module shall use the callout Dcm_ReadMemory to
read the data.c()
[SWS_Dcm_00561] dIf a DID is set as unused (DcmDspDidUsed set to FALSE), the
Dcm shall consider the DID as not supported (according to [SWS_Dcm_00438])c()
[SWS_Dcm_00433] dOn reception of the UDS Service ReadDataByIdentifier (0x22),
for every requested DID the Dcm module shall check if the DID has a Read access con-
figured (see configuration parameter DcmDspDidRead in DcmDspDidInfo). If none

136 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

of the DID has a Read access, the Dcm module shall send NRC 0x31 (Request out of
range).c()
[SWS_Dcm_00434] dOn reception of the UDS Service ReadDataByIdentifier (0x22),
for every requested DID the Dcm module shall check if the DID can be read in the
current session (see configuration parameter DcmDspDidReadSessionRef). If none
of the DID can be renden in the current session, the Dcm module shall send a NRC
0x31 (RequestOutOfRange).c()
[SWS_Dcm_00435] dOn reception of the UDS Service ReadDataByIdentifier (0x22),
for every requested DID the Dcm module shall check if the DID can be read in the cur-
rent security level (see configuration parameter DcmDspDidReadSecurityLevel-
Ref). If not, the Dcm module shall send NRC 0x33 (Security access denied).c()
[SWS_Dcm_00819] dOn reception of the UDS Service ReadDataByIdentifier (0x22),
for every requested DID the Dcm module shall check if the DID can be read in the
current mode condition (according to the configuration parameter DcmDspDidRead-
ModeRuleRef). If not, the Dcm module shall send the calculated negative response of
the referenced DcmModeRule.c()
[SWS_Dcm_00439] dOn reception of the UDS Service ReadDataByIdentifier (0x22),
for every requested DID outside the OBD range (F400-F8FF), the Dcm mod-
ule shall request the application if the DID can be read by calling the config-
ured function (if parameter DcmDspDataUsePort set to USE_DATA_SYNCH_FNC or
USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_FNC_ERROR; see configuration
parameter DcmDspDataConditionCheckReadFnc) on each data of the DID or
call the associated ConditionCheckRead operation (if parameter DcmDspDataUse-
Port set to USE_DATA_SYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_-
SERVER or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR). If not (one function re-
turns E_NOT_OK) , the Dcm module shall send a negative response with NRC set
to value from the parameter "ErrorCode" of DcmDspDataConditionCheckReadFnc
function or ConditionCheckRead operation.c()
Note: This requirement exceeds the standard ConditionCheck behavior as described
by ISO 14229-1 ”NRC handling for ReadDataByIdentifier service” , because it is not
restricted to use NRC 0x22 in a negative response.
[SWS_Dcm_00440] dIf the requested DID references other DID using DcmDsp-
DidRef, the Dcm module shall process the verification and the reading of every ref-
erenced DID and concatenate the response data without any gaps based on the se-
quence in the configuration.c()
[SWS_Dcm_CONSTR_6023] DcmDspDidRef shall not reference the same DID ref-
erence twice dDcmDspDid container shall not include the same DcmDspDidRef pa-
rameters more than once.c()
[SWS_Dcm_CONSTR_6057] Dependency for DcmDspDataEcuSignal dDcmDsp-
DataEcuSignal shall be only present if DcmDspDataUsePort is set to USE_ECU_-
SIGNAL.c()

137 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_CONSTR_6058] Dependency for DcmDspDataEndianness dIn case

DcmDspDataEndianness is not configured, the DcmDspDataDefaultEndianness
shall be used instead.c()
[SWS_Dcm_CONSTR_6061] Dependency for DcmDspDataReadDataLengthFnc
dDcmDspDataReadDataLengthFnc shall be only present if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR
c()
[SWS_Dcm_CONSTR_6062] Dependency for DcmDspDataReadFnc dDcmDsp-
DataReadFnc shall be only present if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR
c()
[SWS_Dcm_01385] dIf the DID dataRecord has bytes, not defined by any data ele-
ment, the Dcm shall fill these bytes with the value 0x00.c()
[SWS_Dcm_01431] dIf the configuration parameter DcmDspDidSize is configured,
the Dcm shall enforce the DID data to have the configured size.c()
[SWS_Dcm_01587] Atomic BndM read operation dAfter all verification (see
[SWS_Dcm_00433], [SWS_Dcm_00434], [SWS_Dcm_00435], [SWS_Dcm_00436])
the Dcm module shall get for every requested DID with DcmDspDidUse-
Port set to USE_ATOMIC_BNDM and outside the OBD range (F400-F8FF)
the data values by reading the data from the associated BlockId from the
BndM (DcmDspDidBndMBlockIdRef) using the block specific reading function
BndM_GetBlockPtr_<BlockId.Shortname>.c(RS_Diag_04243)

7.6.2.6.1 UDS DID

[SWS_Dcm_00578] dOn reception of the UDS Service ReadDataByIdentifier (0x22),

for every requested DID outside the OBD range (F400-F8FF), after all verifica-
tion (see [SWS_Dcm_00433], [SWS_Dcm_00434] and [SWS_Dcm_00435]), If the
data is configured as a "ECU signal" of the IoHwAb (parameter DcmDspDataUse-
Port), the Dcm shall call the Api IoHwAb_Dcm_Read<EcuSignalName >() (param-
eter DcmDspDataReadEcuSignal) to get the Data. In this case, the requirements
[SWS_Dcm_00439], [SWS_Dcm_00436] and [SWS_Dcm_00437] shall not apply.c()

138 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00436] dOn reception of the UDS Service ReadDataByIdentifier (0x22),

for every requested DID outside the OBD range (F400-F8FF), the Dcm module shall
for each signal (DcmDspDidSignal) with a dynamic data length (DcmDspDataType
is set to UINT8_DYN): call either the configured function DcmDspDataReadDataL-
engthFnc (if parameter DcmDspDataUsePort set to USE_DATA_SYNCH_FNC or
USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_FNC_ERROR) or the associated
ReadDataLength operation (if parameter DcmDspDataUsePort set to USE_DATA_-
SYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER or USE_DATA_-
ASYNCH_CLIENT_SERVER_ERROR) to get the data length in byte.c()
[SWS_Dcm_00437] dAfter all verification (see [SWS_Dcm_00433],
[SWS_Dcm_00434], [SWS_Dcm_00435] and [SWS_Dcm_00436]) the Dcm mod-
ule shall get for every requested DID outside the OBD range (F400-F8FF), all the data
values by calling all the configured function (if parameter DcmDspDataUsePort set
to USE_DATA_SYNCH_FNC or USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_-
FNC_ERROR; see configuration parameter DcmDspDataReadFnc) or call all the
associated ReadData operations (if parameter DcmDspDataUsePort set to USE_-
DATA_SYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER or USE_-
DATA_ASYNCH_CLIENT_SERVER_ERROR) or read all the associated SenderReceiver
interfaces (if parameter DcmDspDataUsePort set to USE_DATA_SENDER_RECEIVER
or to USE_DATA_SENDER_RECEIVER_AS_SERVICE).c()
[SWS_Dcm_01432] dAfter all verification (see [SWS_Dcm_00433],
[SWS_Dcm_00434], [SWS_Dcm_00435] and [SWS_Dcm_00436]) the Dcm module
shall get for every requested DID with DcmDspDidUsePort set to USE_ATOMIC_-
SENDER_RECEIVER_INTERFACE, USE_ATOMIC_SENDER_RECEIVER_INTER-
FACE_AS_SERVICE or USE_ATOMIC_NV_DATA_INTERFACE and outside the OBD
range (F400-F8FF) the data values by reading the associated sender-receiver or
NvDataInterface DataServices_{DID}.c()
[SWS_Dcm_00560] dIf the data is configured as a BlockId of the NvRam (parameter
DcmDspDataUsePort), the Dcm shall call the Api NvM_ReadBlock() with the BlockId
(parameter DcmDspDataBlockIdRef)c()
Note : For more information, refer to [15, SWS-NVRAMManager].
[SWS_Dcm_00638] dTo serialize the required AUTOSAR data types (signed- and un-
signed integer) into the response message of ReadDataByIdentifier responses, the
target endianness configured in DcmDspDataEndianness shall be considered for
DcmDspData elements having DcmDspDataUsePort set to USE_DATA_SENDER_-
RECEIVER, USE_DATA_SENDER_RECEIVER_AS_SERVICE, USE_ECU_SIGNAL.c()
[SWS_Dcm_CONSTR_6070] Dependency for DcmDspDataEndianness dIn case
DcmDspDataEndianness is not present, the DcmDspDataDefaultEndianness
shall be used instead.c()

139 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.6.2.6.2 OBD DID

[SWS_Dcm_00481] dOn reception of the UDS Service ReadDataByIdentifier (0x22),

for every requested DID inside the OBD range (F400-F4FF), the Dcm module
shall get the DID value as defined for OBD Service $01 (see [SWS_Dcm_00407],
[SWS_Dcm_00408], [SWS_Dcm_00943], [SWS_Dcm_00621], [SWS_Dcm_00622],
[SWS_Dcm_00623], [SWS_Dcm_00944] and [SWS_Dcm_00718] ), if DcmDspEn-
ableObdMirror is set to true.c()
[SWS_Dcm_00482] dOn reception of the UDS Service ReadDataByIdentifier (0x22),
for every requested DID inside the OBD Monitor range (F600-F6FF), the Dcm mod-
ule shall get the DID value as defined for OBD Service $06 (see [SWS_Dcm_00957],
[SWS_Dcm_00958], [SWS_Dcm_00945] and [SWS_Dcm_00956])c()
[SWS_Dcm_00483] dOn reception of the UDS Service ReadDataByIdentifier (0x22),
for every requested DID inside the OBD InfoType range (F800-F8FF), the Dcm mod-
ule shall get the DID value as defined for OBD Service $09 (see [SWS_Dcm_00422],
[SWS_Dcm_00423] and [SWS_Dcm_00949] without including the number of data
items within the response, if DcmDspEnableObdMirror is set to true.c()
[SWS_Dcm_01195] dIf DcmDspEnableObdMirror is set to true, an explicitly config-
ured DID inside the OBD range (F400-F4FF) and the OBD InfoType range (F800-F8FF)
shall use the UDS interface.c()
[SWS_Dcm_01197] dIf DcmDspEnableObdMirror is set to FALSE, all requests
within the OBD DID range shall use the UDS interface.c()
If DcmDspEnableObdMirror is set to FALSE ([SWS_Dcm_01197]) or the DID is ex-
plicitly configured inside the OBD PID range (F400-F4FF) ([SWS_Dcm_01195]), the
access to the OBD data shall be given in the following way:
[SWS_Dcm_01379] dOn reception of an UDS Service ReadDataByIdentifier (0x22) re-
quest with only ”availability OBDDataIdentifier” as parameter, the Dcm shall respond
with the corresponding supported (=configured) DIDs in the OBD range (F400-F4FF).c
()
[SWS_Dcm_01380] dOn reception of an UDS Service ReadDataByIdentifier (0x22) re-
quest with only OBDDataIdentifier that are not ”availability OBDDataIdentifier”, the
Dcm shall obtain the current value of these OBDDataIdentifier by invoking the con-
figured Xxx_ReadData() functions for every data of the OBDDataIdentifier and shall
return these values as response to Service 0x22.c()
[SWS_Dcm_01381] dOn reception of an UDS Service ReadDataByIdentifier (0x22)
request with a mixture of ”availability OBDDataIdentifier” and not ”availability OBD-
DataIdentifier”, this request shall be ignored by the Dcm.c()
[SWS_Dcm_01382] dIf an OBDDataIdentifier contains support information (presence
of DcmDspDidDataSupportInfo container), the Dcm shall add the support informa-
tion in the diagnostic response.c()

140 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01383] dIf an OBDDataIdentifier contains support information (presence

of DcmDspDidDataSupportInfo container), the Dcm shall calculate the support in-
formation value according to the available data for this DID: for every DcmDspData
container existing for this DID, the associated support information bits, referenced in
DcmDspDidDataSupportInfo, shall be set to one.c()
[SWS_Dcm_01384] dWhen responding to UDS Service ReadDataByIdentifier (0x22)
with OBDDataIdentifier, the Dcm shall put fill-bytes between DcmDspData in the OBD-
DataIdentifier whenever content bytes are missing, in order to fit to the DID size (see
configuration parameter DcmDspDidSize).c()
[SWS_Dcm_01386] dTo serialize the required AUTOSAR data types (signed and
unsigned integer) into the response message of ReadDataByIdentifier (0x22) OBD-
DataIdentifier responses the target endianness configured in DcmDspDataEndian-
ness shall be considered for DcmDspData elements having DcmDspDataUsePort
set to {USE_DATA_SENDER_RECEIVER, USE_DATA_SENDER_RECEIVER_AS_SER-
VICE, USE_ECU_SIGNAL}. In case DcmDspDataEndianness is not present, the
DcmDspDataDefaultEndianness shall be used instead.c()
If DcmDspEnableObdMirror is set to FALSE or the DID is explicitly configured inside
the OBD InfoType range (F800-F8FF), the access to the OBD data shall be given in the
following way:
[SWS_Dcm_01387] dOn reception of an UDS Service ReadDataByIdentifier (0x22) re-
quest with one or more ”availability OBDInfoTypeDataIdentifier” as parameter, the Dcm
module shall respond with the corresponding supported (=configured) DIDs in the OBD
range (F800-F8FF).c()
[SWS_Dcm_01388] dOn reception of an UDS Service ReadDataByIdentifier (0x22) re-
quest with ”availability OBDInfoTypeDataIdentifier” together with other OBDInfoType-
DataIdentifier as parameter, the Dcm module shall ignore the request.c()
[SWS_Dcm_01389] dOn reception of an UDS Service ReadDataByIdentifier (0x22)
request with an OBDInfoTypeDataIdentifier that is not an ”availability OBDInfoType-
DataIdentifier”, the Dcm module shall obtain the value of this OBDInfoTypeDataIdenti-
fier by invoking all the configured Xxx_ReadData() function for every data of this OBD-
InfoTypeDataIdentifier and shall return the value as response to Service 0x22.c()

7.6.2.7 Service 0x24 - ReadScalingDataByIdentifier

[SWS_Dcm_00258] dThe Dcm module shall implement the UDS Service ReadScaling-
DataByIdentifier (0x24)c()
To obtain scaling information, the tester can invoke UDS Service 0x24 with the 2-byte
DID as parameter. The configuration of the Dcm contains for each configured DID:
• The 2-byte DID (see configuration parameter DcmDspDidIdentifier)
• For every data of the DID :

141 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• The function GetScalingInformation (see configuration parameters DcmDsp-

DataGetScalingInfoFnc and DcmDspDataUsePort)
• The length of the ScalingInfo returned by the GetScalingInformation function (see
configuration parameter DcmDspDataScalingInfoSize)
[SWS_Dcm_00394] dOn reception of a request for UDS Service ReadScalingByIden-
tifier, the Dcm module shall call every function Xxx_GetScalingInformation() configured
for everay data of the DID received in the request and return the data received in the
responsec()
[SWS_Dcm_CONSTR_6060] Dependency for DcmDspDataGetScalingInfoFnc
dDcmDspDataGetScalingInfoFnc shall be only present if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR
c()

7.6.2.8 Service 0x27 - SecurityAccess

[SWS_Dcm_00252] dThe Dcm module shall implement the UDS Service SecurityAc-
cess (0x27)c(RS_Diag_04005)
The purpose of this service is to provide a means to access data and/or diagnostic
services, which have restricted access for security, emissions, or safety reasons.
[SWS_Dcm_00321] dIf the request length is correct, the DSP submodule shall check
if the requested subfunction value (access type) is configured in the ECU (see con-
figuration parameter DcmDspSecurityLevel). If the requested subfunction value is
not configured, the DSP submodule shall trigger a negative response with NRC 0x12
(SubFunction not supported).c()
[SWS_Dcm_00323] dIf the requested subfunction value is configured and a service
with subfunction type "requestSeed "(= odd value) has been received and if the re-
quested access type is already active (see Dcm_GetSecurityLevel), the DSP sub-
module shall set the seed content to 0x00.c()
[SWS_Dcm_00324] dIn the other case than the one described in [SWS_Dcm_00323]
(access type is not active or "send key" request), if DcmDspSecurityUsePort is
set to USE_ASYNCH_CLIENT_SERVER, the DSP submodule shall call the configured
operation Xxx_GetSeed() (in case "request seed" is received) or Xxx_CompareKey()
(in case "send key" is received).c()
[SWS_Dcm_00862] dOn reception of the UDS Service SecurityAccess (0x27) with sub-
function type "requestSeed" and if the requested access type is not already active, the
Dcm module shall request a seed by calling the configured Xxx_GetSeed() function (if

142 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

the configuration parameter DcmDspSecurityUsePort is set to USE_ASYNCH_FNC,

refer to configuration parameter DcmDspSecurityGetSeedFnc).c()
Note : If the static seed mechanism is used, the processing needs to be done by the
application implementing the Xxx_GetSeed() and Xxx_CompareKey() functions.
[SWS_Dcm_CONSTR_6077] Dependency for DcmDspSecurityGetSeedFnc d
DcmDspSecurityGetSeedFnc shall be present only if DcmDspSecurityUsePort
is set to USE_ASYNCH_FNC.c()
[SWS_Dcm_00863] dOn reception of the UDS Service SecurityAccess (0x27) with
subfunction type "sendKey", if the requested access type is not already active and
if the "request seed" for the related access type was executed successfully, the
Dcm module shall request the result of a key comparison by calling the configured
Xxx_CompareKey() function (if the configuration parameter DcmDspSecurityUse-
Port is set to USE_ASYNCH_FNC, refer to configuration parameter DcmDspSecuri-
tyCompareKeyFnc).c()
[SWS_Dcm_CONSTR_6075] Dependency for DcmDspSecurityCompareKeyFnc
dDcmDspSecurityCompareKeyFnc shall be configured only if DcmDspSecuri-
tyUsePort is set to USE_ASYNCH_FNC.c()
The following list gives as an example, which errors can be detected by the security
access service and stored in the error code information:
• RequestSequenceError (NRC 0x24), when invalid access type is send at "send
key",
• RequiredTimeDelayNotExpired (NRC 0x37), when time delay is active (see con-
figuration parameter DcmDspSecurityDelayTime),
• ExceededNumberOfAttempts (NRC 0x36), when number of attempts to get secu-
rity access reaches or exceeds the configured limit (see configuration parameter
DcmDspSecurityNumAttDelay), and
• InvalidKey (NRC 0x35), when invalid key is send at "send key".
[SWS_Dcm_00325] dIf the operation CompareKey() returns E_OK, the DSP submod-
ule shall set the new access type with DslInternal_SetSecurityLevel()(see the conver-
sion formula given in ECUC_Dcm_00754 DcmDspSecurityLevel).c()
[SWS_Dcm_01397] dIf Xxx_CompareKey() returns value
DCM_E_COMPARE_KEY_FAILED and DcmDspSecurityNumAttDelay is con-
figured, the Dcm shall increment the attempt counter of the security level for which the
sendKey subfunction request failed.c(RS_Diag_04005)
[SWS_Dcm_00660] dIf Xxx_CompareKey() returns value
DCM_E_COMPARE_KEY_FAILED and if the number of failed attempts to enter
the requested security level (AttemptCounter) is less than the value configured for
the DcmDspSecurityNumAttDelay parameter of the requested security level, the
Dcm module shall send a negative response with NRC 0x35 (InvalidKey) and shall not
change the Dcm internal security level. Note: if DcmDspSecurityNumAttDelay

143 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

parameter is not configured, the number of failed attempts to enter the requested
security level (AttemptCounter) is not considered.c()
[SWS_Dcm_01349] dIf Xxx_CompareKey() returns value
DCM_E_COMPARE_KEY_FAILED and if the number of failed attempts to enter
the requested security level (AttemptCounter) is greater or equal than the value con-
figured for the DcmDspSecurityNumAttDelay parameter of the requested security
level, the Dcm module shall start the SecurityDelayTimer with the value configured in
DcmDspSecurityDelayTime for the SecurityLevel which was requested in the failed
request, send a negative response with NRC 0x36 (exceededNumberOfAttempts) and
shall not change the Dcm internal security level.c()
[SWS_Dcm_01150] dIf Xxx_CompareKey() returns value E_NOT_OK, the Dcm module
shall send a negative response with NRC code equal to the ErrorCode parameter value
and shall not increment the attempt counter or change the Dcm internal security level.c
()
[SWS_Dcm_01350] dWhile the SecurityDelayTimer of SecurityLevel is not yet
elapsed, the Dcm module shall send a negative response with NRC 0x37 (required-
TimeDelayNotExpired) on a SecurityAccess (0x27) requestSeed subfunction request
for that Security Level.c()
[SWS_Dcm_00659] dIf Xxx_GetSeed() returns value E_NOT_OK, the Dcm module
shall send a negative response with NRC code equal to the ErrorCode parameter
value.c()

7.6.2.9 Service 0x28 - CommunicationControl

[SWS_Dcm_00511] dThe Dcm module shall implement the CommunicationControl

(service 0x28) of the Unified Diagnostic Services.c()
[SWS_Dcm_00512] dOn invocation of the sent confirmation function of the UDS Ser-
vice CommunicationControl (0x28) from DSD with the subnet parameter of the request
equal to 0x00, the Dcm shall do for each NetworkHandle (see DcmDspAllComMChan-
nelRef) which is configured in DcmDspComControlAllChannel:
1. trigger the mode switch Dcm_CommunicationControl_<Network> ModeDeclara-
tionGroupPrototype to the mode corresponding the communicationType and con-
trolType parameter from the CommunicationControl request.
2. call the Api BswM_Dcm_CommunicationMode_CurrentState with the parameters
NetworkHandleType and Dcm_CommunicationModeType corresponding to the
communicationType and controlType parameter from the CommunicationControl
request (see Dcm_CommunicationModeType definition).
c()
[SWS_Dcm_00785] dOn invocation of the sent confirmation function of the UDS Ser-
vice CommunicationControl (0x28) from DSD with the subnet parameter of the request

144 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

equal to 0x0F(CommunicationControl on the network which request is received on),

the Dcm shall do for the NetworkHandle (see DcmDslProtocolComMChannelRef) of
the current received DcmDslProtocolRxPduRef:
1. trigger the mode switch Dcm_CommunicationControl_<Network> ModeDeclara-
tionGroupPrototype to the mode corresponding to the communicationType and
controlType parameter from the CommunicationControl request.
2. call the Api BswM_Dcm_CommunicationMode_CurrentState with the parameters
NetworkHandleType and Dcm_CommunicationModeType corresponding to the
communicationType and controlType parameter from the CommunicationControl
request (see Dcm_CommunicationModeType definition)
c()
[SWS_Dcm_00786] dOn invocation of the sent confirmation function of the UDS Ser-
vice CommunicationControl (0x28) from DSD with the subnet parameter of the request
between 0x01 and 0x0E, the Dcm shall check if the received subnet parameter (see
DcmDspSubnetNumber) is supported. In case it is not supported a NegativeResponse
code 0x31 shall be sent. In case it is supported the Dcm shall do for the correspond-
ing NetworkHandle (see DcmDspSpecificComMChannelRef) of the received subnet
parameter (see DcmDspSubnetNumber):
1. trigger the mode switch Dcm_CommunicationControl_<Network> ModeDeclara-
tionGroupPrototype to the mode corresponding the communicationType and con-
trolType parameter from the CommunicationControl request.
2. call the Api BswM_Dcm_CommunicationMode_CurrentState the parameters Net-
workHandleType and with Dcm_CommunicationModeType corresponding the
communicationType and controlType parameter from the CommunicationControl
request (see Dcm_CommunicationModeType definition)
c()
For some use-cases the Dcm may re-enable the CommunicationControl due to external
changed mode conditions:
[SWS_Dcm_00753] dIn case that the referenced ModeRule (see ECUC_Dcm_00943)
is not fulfilled anymore for a NetworkHandle which is currently in a state other than
DCM_ENABLE_RX_TX_NORM_NM, the Dcm shall:
1. switch the mode group Dcm_CommunicationControl_<Network> ModeDeclara-
tionGroupPrototype toDCM_ENABLE_RX_TX_NORM_NM
2. call BswM_Dcm_CommunicationMode_CurrentState with the parameters Net-
workHandleType set to the corresponding NetworkHandle of the network and
RequestedCommunicationMode set to DCM_ENABLE_RX_TX_NORM_NM
c()
[SWS_Dcm_00860] dFor a NetworkHandle which is currently in a state other than
DCM_ENABLE_RX_TX_NORM_NM if the Dcm is transitioning to default session or

145 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

upon any diagnostic session change where the new session does not support UDS
Service CommunicationControl anymore, the Dcm shall:
1. switch the mode group Dcm_CommunicationControl_<Network> ModeDeclara-
tionGroupPrototype to DCM_ENABLE_RX_TX_NORM_NM
2. call BswM_Dcm_CommunicationMode_CurrentState with the parameters Net-
workHandleType set to the corresponding NetworkHandle of the network and
RequestedCommunicationMode set to DCM_ENABLE_RX_TX_NORM_NM
c()
Note: the NetworkHandles to be considered are all ComM channels which are refer-
enced from either DcmDspSpecificComMChannelRef, DcmDspAllComMChannel-
Ref or DcmDspComControlSubNodeComMChannelRef.
[SWS_Dcm_01077] dIf a CommunicationControl Request with the sub-function "en-
ableRxAndDisableTxWithEnhancedAddressInformation" is received, the Dcm shall
check the "nodeIdentification-Number" listed as DcmDspComControlSubNodeId and
for the referenced network (see DcmDspComControlSubNodeComMChannelRef ), it
shall do the followings:
1. trigger the mode switch Dcm_CommunicationControl_<Network> ModeDeclara-
tionGroupPrototype to the mode corresponding the communicationType and con-
trolType parameter from the CommunicationControl request.
2. call the Api BswM_Dcm_CommunicationMode_CurrentState with the parameters
NetworkHandleType and Dcm_CommunicationModeType corresponding to the
communicationType and controlType parameter from the CommunicationControl
request (see Dcm_CommunicationModeType definition).
The analogue controlType enableRxAndDisableTx shall be used with the the following
existing Dcm_CommunicationModeType values:
• DCM_ENABLE_RX_DISABLE_TX_NORM
• DCM_ENABLE_RX_DISABLE_TX_NM
• DCM_ENABLE_RX_DISABLE_TX_NORM_NM.
c()
[SWS_Dcm_01078] dThe Dcm shall trigger a negative response with NRC 0x31
(RequestOutOfRange), if a CommunicationControl Request with the sub-function
"enableRxAndDisableTxWithEnhancedAddressInformation" and a "nodeIdentification-
Number" which is not listed as DcmDspComControlSubNodeId is received.c()
[SWS_Dcm_01079] dIf a CommunicationControl Request with the sub-function "en-
ableRxAndTxWithEnhancedAddressInformation" is received, the Dcm shall check the
"nodeIdentification-Number" listed as DcmDspComControlSubNodeId and for the
referenced network (see DcmDspComControlSubNodeComMChannelRef ) it shall
do the followings:

146 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

1. trigger the mode switch Dcm_CommunicationControl_<Network> ModeDeclara-

tionGroupPrototype to the mode corresponding the communicationType and con-
trolType parameter from the CommunicationControl request.
2. call the Api BswM_Dcm_CommunicationMode_CurrentState with the parameters
NetworkHandleType and Dcm_CommunicationModeType corresponding to the
communicationType and controlType parameter from the CommunicationControl
request (see Dcm_CommunicationModeType definition).
The analogue controlType enableRxAndTx shall be used with this the following existing
Dcm_CommunicationType values :
• DCM_ENABLE_RX_TX_NORM
• DCM_ENABLE_RX_TX_NM
• DCM_ENABLE_RX_TX_NORM_NM.
c()
[SWS_Dcm_01080] dThe Dcm shall trigger a negative response with NRC 0x31 (Re-
questOutOfRange), if a CommunicationControl Request with the sub-function "en-
ableRxAndTxWithEnhancedAddressInformation" and a "nodeIdentification-Number"
which is not listed as DcmDspComControlSubNodeId is received.c()
[SWS_Dcm_01081] dIf DcmDspComControlSubNodeUsed is set to FALSE the sub-
system (DcmDspComControlSubNode) is not available in this configuration.c()
[SWS_Dcm_01082] dIf DcmDspComControlSubNodeUsed is set to TRUE the sub-
system (DcmDspComControlSubNode) is available in this configuration.c()
Note : Condition checks (i.e. NRC 22 checks) on CommunicationType and NetworkType
as well as check of CommunicationType support (i.e. NRC 0x31 check for Communi-
cationType) are not directly supported by the Dcm. Supplier/manufacturer notifications
can be used.

7.6.2.10 Service 0x29 - Authentication

The UDS service Authentication (0x29) is used to provide dynamic means to control
the access to diagnostic services. Execution of certain diagnostic services might have
impact on safety, emissions or the vehicle. Controlling the access to diagnostic ser-
vices via certificates provide means to control the access to diagnostic services after
production. The access to these resources can be limited in time or bound to certain
vehicles or ECUs only. AUTOSAR Dcm provides an out of the box solution for authen-
ticated diagnostics with a given semantics of the UDS service Authentication. Even
ISO 14229-1 [x] leaves more freedom, the Dcm will use only the functionality specified
in this chapter. Further interpretations, certificate types or certificate content are out
of scope of the AUTOSAR Dcm module. At the point of time this specification was de-
veloped, only the DIS (Draft International Standard) of ISO 14299-1:2018 is available.

147 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Unless the official international standard ISO 14299-1:2018 is released, AUTOSAR will
implement a solution based on this not public available draft.
[SWS_Dcm_01559] Support of UDS service authentication dThe Dcm shall imple-
ment the UDS service Authentication (0x29) for sub-functions:
• deAuthenticate
• verifyCertificateUnidirectional
• verifyCertificateBidirectional
• proofOfOwnership
• authenticationConfiguration
c(RS_Diag_04230)
Note: AUTOSAR Dcm only implements the authentication via PKI certificated ex-
change. Authentication with challenge-response (ACR) is out of scope of AUTOSAR.
If it is required it needs a full custom implementation using existing Dcm callouts for
custom service processing.
[SWS_Dcm_01551] NRC Handling for UDS service authentication dThe Dcm shall
follow the NRC handling as defined for ISO 14229-1:2018 for UDS service authenti-
cation. This includes the NRC codes as well as the order of individual NRC checks.c
(RS_Diag_04230)
[SWS_Dcm_CONSTR_6091] Authentication configuration dThe presence of a
DcmDsdService with DcmDsdSidTabServiceId set to 0x29, requires a configured con-
tainer DcmDspAuthentication on DcmDsp.c()
[SWS_Dcm_CONSTR_6092] Authentication per connection dThe presence of a
DcmDsdService with DcmDsdSidTabServiceId set to 0x29, requires a configured
DcmDspAuthenticationConnection per configured connection DcmDslConnection.c()
[SWS_Dcm_CONSTR_6093] One authentication configuration per connection
dEach DcmDspAuthenticationConnection shall refer a different DcmDslMainConnec-
tion by the reference in DcmDspAuthenticationConnectionMainConnectionRef.c()
The Dcm is using the Csm and KeyM for certificate management. Parsing the certifi-
cate is a potential time-consuming operation and needs to be executed asynchronous.
There are opinions that security shall not reveal any cause of failed authentication and
thus have no dedicated NRCs for different certificate failures. To respect this use case
the Dcm provides a general security NRC handling.
[SWS_Dcm_01560] Use of generic NRC for invalid certificate or content dIf the
mode referenced by DcmDspAuthenticationGeneralNRCModeRuleRef evaluates to
true, the Dcm shall send the NRC code given in DcmDspAuthenticationGeneralNRC
instead of the specific NRC codes in all situation where a Certificate verification failed
- NRC is returned.c(RS_Diag_04230)

148 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_CONSTR_6094] Generic NRC configuration requirements dIf

DcmDspAuthenticationGeneralNRCModeRuleRef is configured the parameter
DcmDspAuthenticationGeneralNRC shall also be configured.c(RS_Diag_04230)

7.6.2.10.1 De-authentication

The de-authenticate sub-function shall be always available if service 0x29 is used. This
service set the authentication state to deauthenticated for the diagnostic connection the
request was received on.
[SWS_Dcm_CONSTR_6095] dThe presence of a DcmDsdService with DcmDsd-
SidTabServiceId set to 0x29, requires a DcmDsdSubService on this DcmDsdService
with DcmDsdSubServiceId set to deAuthenticate.c()
[SWS_Dcm_01561] Deauthentication by diagnostic service request dOn reception
of an Authentication (0x29) service with sub-function equal to de-authenticate, the Dcm
shall set the authentication state to deauthenticated on the connection the Dcm has
received that request.c(RS_Diag_04230)
[SWS_Dcm_01565] dOn reception of an Authentication (0x29) service with sub-
function equal to de-Authenticate, the Dcm shall reply with a positive response having
the authenticationReturnParameter set to DeAuthentication successful.c(RS_Diag_-
04230)

7.6.2.10.2 Verify Certificates

[SWS_Dcm_01459] Supported communicationConfiguration dOn reception of an

Authentication (0x29) service with sub-function equal to verifyCertificateUnidirectional
or verifyCertificateBidirectional, the Dcm shall reply with an NRC 0x31 (requestOut-
OfRange) if the communicationConfiguration (COCO) parameter has a value different
than 0x00.c(RS_Diag_04230)
The support of a COCO with constant value of 0x00 implies that no session key is
supported by the Dcm. Upon receiving an authentication request with sub-function ver-
ifyCertificateUniDirectional and the communicationConfiguration (COCO) set to 0x00,
the Dcm starts to verify the certificate. This service is implemented on BSW level by in-
tention, to reduce the possible dialects of service 0x29 to what is natively supported by
AUTOSAR. The Csm [16] and KeyM [17] modules allow to use different cryptographic
methods. It is part of the Dcm strategy to explicitly require that certificates and all kind
of access to information inside are handled by the Csm and its configuration. This
allows to map different kind of certificates with different levels of security to the Dcm,
thus abstracting the certificate complexity from Dcm.
[SWS_Dcm_01460] Verify verifyCertificateUnidirectional message length check
dOn reception of an Authentication (0x29) service with sub-function equal to verifyCer-
tificateUnidirectional, the Dcm shall verify that the message length fits to the size given

149 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

in the parameters lengthOfCertificateClient and return a NRC 0x13 if the size does not
match.c(RS_Diag_04230)
[SWS_Dcm_01461] Verify verifyCertificateBidirectional message length check
dOn reception of an Authentication (0x29) service with sub-function equal to verifyCer-
tificateBidirectional, the Dcm shall verify that the message length fits to the size given
in the parameters lengthOfCertificateClient and lengthOfChallengeClient and return a
NRC 0x13 if the size does not match. The Dcm uses the lengthOfCertificateClient as
offset to calculate the position of lengthOfChallengeClient.c(RS_Diag_04230)
[SWS_Dcm_01462] Required configuration for bidirectional authentication dIf the
sub-function verifyCertificateBidirectional is configured in the DsdServiceSubFunc-
tion for 0x29, the configuration parameters DcmDspAuthenticationECUCertifi-
cateRef and DcmDspAuthenticationECUCertificateKeyElementRef are re-
quired.c()
[SWS_Dcm_01579] Mandatory certificate data dOn reception of an Authentication
(0x29) service with sub-function equal to verifyCertificateUnidirectional or verifyCertifi-
cateBidirectionaland a lengthOfCertificateClient equal to zero, the Dcm shall respond
with NRC 0x13 (incorrectMessageLengthOrInvalidFormat)..c(RS_Diag_04230)
Store certificate in Csm
[SWS_Dcm_01463] Certificate validation dOn reception of an Authentication (0x29)
service with sub-function equal to verifyCertificateUnidirectional or verifyCertificate-
Bidirectional, the Dcm shall use the KeyM API KeyM_SetCertificate to store the client
certificate from the service request within the KeyM module. The following parameter
values shall be used:
• CertificateId = DcmDspAuthenticationConnectionCertificateRef ->
KeyMCertificate.KeyMCertificateId
• certificateDataPtr.certData = Pointer to certificateClient from Request
• certificateDataPtr.certDataLength = lengthOfCertificateClient from Request
c(RS_Diag_04230)
Diagnostic certificate configuration is a task that is mainly executed in the Csm and
KeyM modules. The Dcm provides an abstraction from these modules and only keeps
symbolic references to containers that keep the information. Please take attention
while configuring the Csm and KeyM ’in spirit of Dcm certificates’.
[SWS_Dcm_01464] Invalid certificate size failure dIf the API KeyM_SetCertificate
returns KEYM_E_SIZE_MISMATCH, the Dcm shall return the NRC 0x13 (incorrectMes-
sageLengthOrInvalidFormat).c(RS_Diag_04230)
[SWS_Dcm_01465] Behavior on busy crypto operation dIf any of the Csm or KeyM
APIs called by the Dcm is returning CRYPTO_E_BUSY or KEYM_E_BUSY, the Dcm
shall return the NRC 0x21 (busyRepeat).c(RS_Diag_04230)

150 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01466] Csm APIs returning failure code behavior dThroughout this

chapter the Csm or KeyM are used to process the authentication requests. These
APIs have return values for failures. Unless there is no dedicated requirement for a
given return value and if the return value is different to E_OK, the Dcm shall return a
NRC 0x10 ’GeneralReject’.c(RS_Diag_04230)
The cryptographic operations have potential long execution times and are called asyn-
chronously.
[SWS_Dcm_01467] Asynchronous certificate operation handling dFor all asyn-
chronous Csm or KeyM operations, the Dcm shall wait until the callback has been
called, indicating a successful job termination. If the result (e.g. KeyM_ResultType) is
E_OK, the Dcm shall continue to process the 0x29 request, if the result is different to
E_OK, the Dcm shall skip the further processing and return a negative response with
NRC ’GeneralReject’.c(RS_Diag_04230)
Parse and Verify certificate in Csm
[SWS_Dcm_01468] Verifying client certificate dAfter the Dcm has set the certifi-
cate according to [SWS_Dcm_01463], the Dcm shall verify the certificate by calling
KeyM_VerifyCertificate with the following parameters:
• CertificateId = DcmDspAuthenticationConnectionCertificateRef ->
KeyMMCertificate.KeyMCertificateId
c(RS_Diag_04230)
[SWS_Dcm_01469] Behavior on failed certificate verification dAfter the Dcm has
verified a certificate and KeyM_ReturnType is set to KEYM_E_SIGNATURE_FAIL, the
Dcm shall send a negative response with NRC set to ’Certificate verification failed -
Invalid Signature’.c(RS_Diag_04230)
[SWS_Dcm_01470] Check certificate chain of trust dIf the operation started in
[SWS_Dcm_01468] returns a result of KEYM_E_INVALID_CHAIN_OF_TRUST, the
Dcm shall refuse the client certificate and return a negative response with NRC ’Certifi-
cate verification failed - Invalid Chain of Trust’.c(RS_Diag_04235)
[SWS_Dcm_01471] Check certificate type dIf the operation started in
[SWS_Dcm_01468] returns a result of KEYM_E_INVALID_TYPE, the Dcm shall
refuse the client certificate and return a negative response with NRC ’Certificate
verification failed - Invalid Type’.c(RS_Diag_04235)
[SWS_Dcm_01472] Check certificate format dIf the operation started in
[SWS_Dcm_01468] returns a result of KEYM_E_INVALID_FORMAT, the Dcm shall
refuse the client certificate and return a negative response with NRC ’Certificate ver-
ification failed - Invalid Format’.c(RS_Diag_04235)
[SWS_Dcm_01473] Check certificate format dIf the operation started in
[SWS_Dcm_01468] returns a result of KEYM_E_INVALID_CONTENT, the Dcm shall
refuse the client certificate and return a negative response with NRC ’Certificate verifi-
cation failed - Invalid Scope’.c(RS_Diag_04235)

151 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Note: While most of the KeyM return values can be mapped 1:1 on UDS NRC values,
this does not apply for KEYM_E_INVALID_CONTENT. An invalid content from KeyM
indicates that a key element verification has failed. A failed key element verification
means that the certificate itself is valid, but the KeyM refuses the certificate as the
data does not fit to the server’s required value. In UDS this is expressed by ’Certificate
verification failed - Invalid Scope’. As result invalid content from KeyM will trigger the
NRC invalid scope.
[SWS_Dcm_01475] Check certificate format dIf the operation started in
[SWS_Dcm_01468] returns a result of KEYM_E_CERTIFICATE_REVOKED, the Dcm
shall refuse the client certificate and return a negative response with NRC ’Certificate
verification failed - Invalid Certificate (revoked)’.c(RS_Diag_04235)
[SWS_Dcm_01476] Check certificate valid until dIf the operation started in
[SWS_Dcm_01468] returns a result of KEYM_E_VALIDITY_PERIOD_FAIL, the Dcm
shall refuse the client certificate and return a negative response with NRC ’Certificate
verification failed - Invalid Time Period’.c(RS_Diag_04235)
Verify target identification
Certificates can have target constraints, such as limiting a certificate to a certain VIN
or ECU version number. This is realized by target identification blocks as elements of
the certificate. A target identification block is evaluated at runtime, only if all items are
fulfilled, the certificate is accepted by the Dcm. Each target identification element is
mapped to a compare value of a DcmModeCondition. A DcmModeRule combines
these conditions to one term that evaluates to true or false.
[SWS_Dcm_01490] Certificate acceptance by target identification dThe Dcm shall
only accept certificates if the configured mode rule referenced by DcmDspAuthen-
ticationTargetIdentificationModeRuleRef is evaluated to true.c(RS_Diag_-
04236)
[SWS_Dcm_01491] Behavior on failed target identification dIf the config-
ured mode rule referenced by DcmDspAuthenticationTargetIdentification-
ModeRuleRef is evaluated to fail, the Dcm shall refuse the certificate and send a
negative response with NRC ’Certificate verification failed - Invalid Scope’.c(RS_Diag_-
04236)
[SWS_Dcm_01492] Invalid target identification block data dIf the Dcm fails to match
the target identification block data from DcmModeConditionConnectionCertificateCom-
pareElementRef as valid (e.g. number of required bytes do not match), the Dcm shall
send a negative response with NRC ’Certificate verification failed - Invalid Format’.c
(RS_Diag_04236)
Providing the server challenge
The Dcm uses the Csm to create a server challenge by returning a random value.
[SWS_Dcm_01588] Length of server challenge dThe Dcm shall create a server
challenge with the length configured in DcmDspAuthenticationEcuChallenge-
Length.c(RS_Diag_04230)

152 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01493] Creating the server challenge dAfter successfully validating the

client certificate in [SWS_Dcm_01463], the Dcm shall create a server challenge by
using the Csm in the following sequence:
1) Call of Csm_RandomGenerate with parameters
a. jobId : DcmDspAuthenticationRandomJobRef -> CsmJobId
2) Wait until the asynchronous job has terminated according to [SWS_Dcm_01467].
c(RS_Diag_04230)
The API Csm_RandomGenerate requires an initialised random generator. The initial-
ization of the random generator is a task of the system (integrator).
[SWS_Dcm_01503] Sending positive response on verifyCertificateUniDirectional
dIf the Dcm has successfully calculated server challenge the Dcm shall send a positive
response for the verifyCertificateUniDirectional request with the following parameter
values:
authenticationReturnParameter : ’Certificate verified, Ownership verification neces-
sary’
lengtfOfChallengeServer: length of the challenge generated in [SWS_Dcm_01493]
challengeServer: challenge generated in [SWS_Dcm_01493]
lengthOfEphemeralPublicKeyServer: 0x0000
c(RS_Diag_04230)
Processing a diagnostic request verifyCertificateBidirectional will furthermore require
the Dcm to send a server certificate and signing the client challenge. Therefore, the
following steps are done additionally for verifyCertificateBidirectional.
[SWS_Dcm_01504] Signing client challenge dOn reception of an Authentication
(0x29) service with sub-function equal to verifyCertificateBidirectional, the Dcm shall
sign the received client challenge by calling Csm_SignatureGenerate with the follow-
ing parameter values:
jobId: DcmDspAuthenticationClientChallengeSignJobRef -> CsmJobId
mode: CRYPTO_OPERATIONMODE_SINGLECALL
dataPtr: Pointer to challengeClient in request
dataLength: lengthOfChallengeClient from request
resultPtr: Dcm sided buffer to store the proofOfOwnershipServer
resultLengthPtr: Response data for lengthOfProofOfOwnershipServer
c(RS_Diag_04230)
[SWS_Dcm_CONSTR_6096] Require asynchronous client challenge signing d
DcmDspAuthenticationClientChallengeSignJobRef shall be only accepted if
the referenced CsmJob itself:
• has a CsmProcessingMode set to CRYPTO_PROCESSING_ASYNC
• references a CsmPrimitive with an aggregated CsmSignatureGenerate.
c(RS_Diag_04230)
[SWS_Dcm_01506] Providing the server certificate dOn reception of an Au-
thentication (0x29) service with sub-function equal to verifyCertificateBidirectional,

153 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

the Dcm shall provide the server certificate in the response. The Dcm shall call
KeyM_GetCertificate with the following parameters:
certId: DcmDspAuthenticationECUCertificateRef/KeyMCertificateId
certificateDataPtr: Dcm implementation specific
c(RS_Diag_04230)
[SWS_Dcm_01507] Server certificate size check dIf the API Csm_GetKeyElement
returns CRYPTO_E_SMALL_BUFFER, the Dcm shall return NRC 0x14 (responseToo-
Long).c(RS_Diag_04230)
[SWS_Dcm_01508] Sending positive response on verifyCertificateBidirectional
dIf the Dcm has successfully calculated server challenge, the server challenge and the
server certificate, the Dcm shall send a positive response for the verifyCertificateBidi-
rectional request with the following parameter values:
authenticationReturnParameter: ’Certificate verified, Ownership verification neces-
sary’
lengtfOfChallengeServer: length of the challenge generated in [SWS_Dcm_01493]
challengeServer: challenge generated in [SWS_Dcm_01493]
lengthOfCertificateServer: length of the certificated provided in [SWS_Dcm_01506]
certificateServer: certificated provided in [SWS_Dcm_01506]
lengthOfProofOfOwnershipServer: length of proof-of-ownership server created in
[SWS_Dcm_01504]
proofOfOwnershipServer: proof-of-ownership server created in [SWS_Dcm_01504]
lengthOfEphemeralPublicKeyServer: 0x0000
c(RS_Diag_04230)

7.6.2.10.3 Proof of ownership client

[SWS_Dcm_01509] Sequence check dOn reception of an Authentication (0x29) ser-

vice with sub-function equal to proofOfOwnership and if on this connection the most
recent processed verifyCertificateUnidirectional or verifyCertificateBidirectional service
failed or no such sub-function was processed yet, the Dcm shall send the negative
response ’requestSequenceError’. The connection shall remain in de-authenticated
state.c(RS_Diag_04230)
[SWS_Dcm_01510] Proof of ownership message length check dOn reception of an
Authentication (0x29) service with sub-function equal to proofOfOwnership, the Dcm
shall verify that the message length fits to the size given in the parameters length-
OfProofOfOwnershipClient and lengthOfEphemeralPublicKeyClient and return a NRC
0x13 if the size does not match.c(RS_Diag_04230)
[SWS_Dcm_01511] Client proof of ownership verification dOn reception of an
Authentication (0x29) service with sub-function equal to proofOfOwnership, the Dcm
shall verify the client’s proof of ownership data provide in the request by calling
Csm_SignatureVerify with the following in-parameters:
jobId: DcmDspAuthenticationVerifyProofOfOwnerShipClientJobRef ->
CsmJob.CsmJobId

154 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

mode: set to CRYPTO_OPERATIONMODE_SINGLECALL

dataPtr: challenge generated [SWS_Dcm_01493]
dataLength: length of the challenge generated in [SWS_Dcm_01493]
signaturePtr: proofOfOwnerShipClient from request
signatureLength: lengthOfProofOfOwnerShipClient from request
c(RS_Diag_04230)
[SWS_Dcm_CONSTR_6098] Require asynchronous signature verification d
DcmDspAuthenticationVerifyProofOfOwnerShipClientJobRef is only valid
if the referenced CsmJob itself:
• has a CsmProcessingMode set to CRYPTO_PROCESSING_ASYNC
• references a CsmPrimitive with an aggregated CsmSignatureVerify.
c()
[SWS_Dcm_01512] Failed ownership verification dIf the result of
Csm_SignatureVerify from [SWS_Dcm_01511] is Crypto_VerifyResultType equal
to CRYPTO_E_VER_NOT_OK, the Dcm shall send a negative response with NRC
’Ownership verification failed’.c(RS_Diag_04230)
[SWS_Dcm_01513] SessionKey support dUpon sending a positive response for an
authentication request with sub-function equal to proofOfOwnership, the Dcm shall:
• set all bytes of lengthOfSessionKeyInfo to 0x00
• omit the sessionKeyInfo
c(RS_Diag_04230)
Set current role
[SWS_Dcm_01514] Update the current role dIf the proof of ownership verification
in [SWS_Dcm_01511] was successful and resulted in CRYPTO_E_VER_OK, the Dcm
shall use the value read from the certificate extension DcmDspAuthentication-
RoleElementRef as new role for the current authenticated state.c(RS_Diag_04233)
[SWS_Dcm_01515] Role size check dIf the size of the read role information in
[SWS_Dcm_01514] is different than the size in DcmDspAuthenticationRoleSize,
the Dcm shall send a negative response with NRC ’Certificate verification failed - Invalid
Content’.c(RS_Diag_04230)
Set white list
[SWS_Dcm_01516] Update the current whitelist dIf the proof of ownership verifica-
tion in [SWS_Dcm_01511] was successful and resulted in CRYPTO_E_VER_OK, the
Dcm shall use the white list read from the certificate according to [SWS_Dcm_01517]
as new white list for the current authenticated state.c(RS_Diag_04232)

155 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01517] White list access dTo read the white list from a certificate,
the Dcm shall read all child elements from the referenced DcmDspAuthentica-
tionWhiteListServicesElementRef, DcmDspAuthenticationWhiteList-
DIDElementRef, DcmDspAuthenticationWhiteListRIDElementRef and
DcmDspAuthenticationWhiteListMemorySelectionElementRef certifi-
cate data, by repeating calling the sequence of KeyM_CertElementGetFirst and
KeyM_CertElementGetNext until no further child element is available. The Dcm shall
use the following in parameter values:
certId: DcmDspAuthenticationConnectionCertificateRef -> KeyMCertifi-
cate.KeyMCertificateId
certElementId: DcmDspAuthenticationWhiteListMemorySelectionElemen-
tRef -> KeyMCertificateElement.KeyMCertificateElementId
c()
[SWS_Dcm_01518] White list size check dIf the size of the read white list infor-
mation in [SWS_Dcm_01516] is larger than the size in DcmDspAuthentication-
WhiteListMemorySelectionMaxSize, the Dcm shall send a negative response
with NRC ’Certificate verification failed - Invalid Content’.c(RS_Diag_04230)
[SWS_Dcm_CONSTR_6087] Required size for white lists dIf any of the optional
DcmDspAuthenticationWhiteListMemorySelectionElementRef are config-
ured, the corresponding DcmDspAuthenticationWhiteListMemorySelection-
MaxSize shall be configured for that white list.c(RS_Diag_04232)

7.6.2.10.4 Definition and verification of roles

The roles transmitted inside the certificates are used to assign a tester on one con-
nection one or more roles. A single role itself is presented by a certain bit within the
bitfield representation of the role. Within the Dcm there is static role assignment to each
diagnostic service. A service can be executed if at least one role (bit) assigned to a
service matches a role (bit) in the certificate.
[SWS_Dcm_CONSTR_6088] Supported role sizes dThe parameter DcmDspAu-
thenticationRoleSize defines the size in bytes used in both, certificates and ECU
internal static role configuration. All role parameters (e.g. DcmDspServiceRole) shall
have values that would fit in the amount of bytes given by DcmDspAuthentication-
RoleSize.c(RS_Diag_04233)
[SWS_Dcm_01521] Integer interpretation of roles in certificates dThe Dcm shall
interpret all configured role integer values in the little endian format.c(RS_Diag_04234)
[SWS_Dcm_01522] Role verification dUpon each role verification, the Dcm shall
make a bitwise ’and’ operation on the role provided in the certificate for that connection
and the role assigned to the service. If the result is greater than 0, the Dcm shall treat
the service as allowed to be executed.c(RS_Diag_04233; RS_Diag_04234)

156 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01523] Failed role verification dUpon each role verification, the Dcm
shall make a bitwise ’and’ operation on the role provided in the certificate for that con-
nection and the role assigned to the service. If the result is equal to 0, the Dcm shall
stop the processing of that service and send a negative response ’authenticationRe-
quired’.c(RS_Diag_04233; RS_Diag_04234)
An example of roles in certificates and services with assigned certificates is given in
Figure 7.10. The provided certificate uses 1 byte for roles, with 5 role definitions in.
The certificate will grant the tester rights for the roles ’AfterSales’ and ’ExtendedUser’.
With that certificate, the tester can execute the services that have the corresponding
permissions to be executed in that roles. In that example, the service 0x28 and 0x11
01 are both allowed to be executed. The routine with identifier 0x5678 is only allowed
to be executed in role ’production’, the Dcm will deny the execution with NRC ’authenti-
cationRequired’.

Figure 7.10: Example for roles

7.6.2.10.5 Definition and verification of white lists

Besides the use of roles, the certificates can get extended with optional white lists
for service execution. This allows the issuer of the certificate to extend the range of
allowed services without updating the access lists in the ECU.
The white list is build out of the following elements:
• List of allowed services, 1-4 byte each
• List of allowed data identifiers (DID) and access information, 3 byte each
• List of allowed routine identifiers (RID) and access information, 3 byte each
• List of allowed user defined fault memories, 1 byte each
Parsing and access to the different elements of the white lists is done by
invoking KeyM_CertElementGetFirst and KeyM_CertElementGetNext according to
[SWS_Dcm_01517].

157 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01524] White list for services definition dThe white list for services
is a set of values, each consisting of up to 4 bytes. Each value itself contains the
first bytes of a diagnostic service that is allowed be executed.c(RS_Diag_04233; RS_-
Diag_04234)
Example:
In the following example, a white list section within a certificate is shown. It contains 5
additional services that can be executed:

1 ...
2 SEQUENCE (1 elem)
3 SEQUENCE (2 elem)
4 OBJECT IDENTIFIER 3.9.3.345.3.1.3453.24.3.9.355.73
5 SET (6 elem)
6 OCTET STRING (1 byte) 85
7 OCTET STRING (2 byte) 1101
8 OCTET STRING (3 byte) 22123A
9 OCTET STRING (3 byte) 2E123A
10 OCTET STRING (4 byte) 310113F4
11 SEQUENCE (3 elem) ....

This will allow the Dcm to execute:

• Service 0x85 (with any sub-subfunction and DTCSettingControlOptionRecord

byte)
• Service 0x11 01
• Read and WriteDataByIdentifier for DID 0x123A
• Routine Start for RID 0x13F4
Checks for white lists for services are all done at DSD level. The Dcm checks if the first
bytes of a received diagnostic request match the values allowed by the white list. If a
white list entry exists where all bytes are matching the first bytes of the request, the
service is granted access.
For all other white lists, the Dcm performs the checks at DSP level in the corresponding
service processors.
Please note that it is possible to allow a DID execution in two places in the white list: 1)
as 3 byte service and 2) as DID in the DID list. The difference is that the service checks
only the first 3 bytes of the PDU and will not detect the DID being used in multiple DID or
dynamically defined DID requests, while the DID list element is verified in all services
requesting the DID.
[SWS_Dcm_01525] White list definition for DIDs dThe white list for DIDs defines the
set of data identifiers that are allowed to be read, written and controlled. Each entry
shall contain in the first two bytes the DID number and in the third byte the following
access definitions:

158 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• Bit 0: Read access

• Bit1: Write access
• Bit2: Control access (by InputOutputControlByIdentifier)
A bit value of 0 means that the operation is forbidden, a bit value of 1 means that the
operation is allowed. All not used bits (3-7) shall be set to zero.
DID numbers are always in big endian format (MSB first).c(RS_Diag_04233; RS_-
Diag_04234)
Example:

DID access record Grants access to

0x1A90 0x01 All read data by identifier operations for DID 0x1A90
0x314F 0x05 All read data by identifier and IOcontrol operations for DID
0x314F

DID read operations are performed from various UDS services. Dcm checks on each
DID read the access to that DID.
[SWS_Dcm_01526] White list definition for RIDs dThe white list for RIDs defines
the set of routine identifiers that have access to the sub-functions startRoutine, sto-
pRoutine and requestRoutineResult. Each entry shall contain in the first two bytes the
RID number and in the third byte the following access definitions:
• Bit 0: Access to sub-function ’startRoutine’
• Bit1: Access to sub-function ’stopRoutine’
• Bit2: Access to sub-function ’requestRoutineResult’
A bit value of 0 means that the sub-function is forbidden, a bit value of 1 means that
the sub-function is allowed. All not used bits (3-7) shall be set to zero.
RID numbers are always in big endian format (MSB first).c(RS_Diag_04233; RS_-
Diag_04234)
Example:

RID access record Grants access to

0x0240 0x01 StartRoutine is allowed for RID 0x0240
0x028A 0x07 All routine sub-functions are allowed for RID 0x28A

[SWS_Dcm_01527] White list definition for MemorySelection dThe white list mem-
ory selection is used for the UDS service 0x19 with sub-functions 0x17, 0x18 and 0x19.
The value in the white list defines the accepted parameter values for MemorySelection
in the UDS request.c(RS_Diag_04233; RS_Diag_04234)
Transition into authenticated session

159 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01528] Transition into authenticated state dIf the proof of

ownership verification in [SWS_Dcm_01511] was successful and resulted in
CRYPTO_E_VER_OK and after the role and white list setting was done, the
Dcm shall set the DcmAuthenticationState_{Channel} on that connection into
DCM_AUTHENTICATED.c(RS_Diag_04230)
[SWS_Dcm_01529] Successful ownership verification dIf the result of
Csm_SignatureVerify from [SWS_Dcm_01511] is Crypto_VerifyResultType equal
to CRYPTO_E_VER_OK, the Dcm shall send a positive response with authentication-
ReturnParameter set to ’Ownership verified, Authentication complete’ and providing a
size of 0 for lengthOfSessionKeyInfo and no sessionKeyInfo.c(RS_Diag_04230)
[SWS_Dcm_01530] Persisting authentication state dIf the result of
Csm_SignatureVerify from [SWS_Dcm_01511] is Crypto_VerifyResultType equal
to CRYPTO_E_VER_OK and the mode rule referenced by DcmDspAuthentica-
tionPersistStateModeRuleRef is evaluated to true, the Dcm shall persist the
authentication state, role and white list on that connection.c(RS_Diag_04230)
[SWS_Dcm_01531] Activation of role and white list dThe DCM shall consider the
role and white list for access control only, if the DCM is in authenticated state.c()
[SWS_Dcm_01532] Re-entering authenticated state dIf the Dcm is already in au-
thenticated state while a transition to authentication stated is requested according to
[SWS_Dcm_01529], the Dcm shall overwrite the roles and white list and use only the
role and white last from the last received certificate.c(RS_Diag_04230)

7.6.2.10.6 AuthenticationConfiguration

[SWS_Dcm_01533] Providing the authentication configuration dIf DcmDspAu-

thentication is configured and an Authentication (0x29) service with sub-
function equal to authenticationConfiguration is received, the Dcm shall send a posi-
tive response with authenticationReturnParameter set to ’AuthenticationConfiguration
APCE’.c(RS_Diag_04230)

7.6.2.11 Service 0x2A - ReadDataByPeriodicIdentifier

[SWS_Dcm_01093] Minimum length check for ReadDataByPeriodicIdentifier dOn

reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A), the Dcm module
shall check the request minimum length. If length of the request is wrong, the Dcm
module shall send a NRC 0x13 (Incorrect message length or invalid format).c(RS_-
Diag_04215)
[SWS_Dcm_01552] Read Periodic DID authentication check for statically defined
DIDs dOn reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A), the Dcm
shall check if the access to all static defined requested DIDs is authenticated and read
the data identifiers periodically only if:

160 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• a DcmDspDidReadRole is configured for that DID and the verification according

to [SWS_Dcm_01522] was successful or
• the active white list on that connection has for each requested DID one entry with
read access that matches that DID.
c(RS_Diag_04233)
[SWS_Dcm_01553] Read Periodic DID authentication check for dynamically de-
fined DIDs dOn reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A),
the Dcm shall check if the access to all dynamically defined requested DIDs if the con-
tent is based of DIDs or parts of DIDs is authenticated and read the data identifiers
periodically only if:
• a DcmDspDidReadRole is configured for that DID and the verification according
to [SWS_Dcm_01522] was successful or
• the active white list on that connection has for each requested DID one entry with
read access that matches that DID.
c(RS_Diag_04233)
According to [SWS_Dcm_01537] the authentication checks are only executed if
DcmDspAuthentication is configured. In case of a failed authentication the NRC han-
dling is according to [SWS_Dcm_01544] and [SWS_Dcm_01551] applies.
[SWS_Dcm_00721] Session check for ReadDataByPeriodicIdentifier DID dOn re-
ception of the UDS Service ReadDataByPeriodicIdentifier (0x2A), for every requested
periodicDIDs, the Dcm module shall check if the periodicDID can be read in the current
session (see configuration parameter DcmDspDidReadSessionRef). If none of the
periodicDID can be read in the current session, the Dcm module shall send a NRC 0x31
(RequestOutOfRange).c(RS_Diag_04215)
[SWS_Dcm_00722] Security level check for ReadDataByPeriodicIdentifier DID
dOn reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A), for every re-
quested periodicDIDs, the Dcm module shall check if the periodicDID can be read
in the current security level (see configuration parameter DcmDspDidReadSecu-
rityLevelRef). If not, the Dcm module shall send NRC 0x33 (Security access de-
nied).c(RS_Diag_04215)
[SWS_Dcm_00820] Mode condition check for ReadDataByPeriodicIdentifier DID
dOn reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A), for every
requested periodicDIDs, the Dcm module shall check if the periodicDID can be
read in the current mode condition (see configuration parameter DcmDspDidRead-
ModeRuleRef). If not, the Dcm module shall send the calculated negative response
code of the reference DcmModeRulec(RS_Diag_04215)
[SWS_Dcm_01097] Checks for DDDIDs in ReadDataByPeriodicIdentifier dOn
reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A), if verifica-
tion has been successfully done ([SWS_Dcm_00721], [SWS_Dcm_00722] and
[SWS_Dcm_00820]), and if the request contains one or more dynamically defined

161 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DID(s), the Dcm module shall do the session, security and mode dependencies checks
for all source data in case the configuration parameter DcmDspDDDIDcheckPer-
SourceDID is set to TRUE.c(RS_Diag_04215)
[SWS_Dcm_01098] Condition check for ReadDataByPeriodicIdentifier DID dOn
reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A), for every requested
periodicDIDs, the Dcm module shall invoke the ConditionCheckRead operation (or the
respective C-Function) if configured. In case of a negative result, the returned Error-
Code shall be used as final negative response code.c(RS_Diag_04215)
[SWS_Dcm_01099] Support of dynamic length DIDs dOn reception of the UDS Ser-
vice ReadDataByPeriodicIdentifier (0x2A), for every requested periodicDIDs, with a
configured dynamic length the Dcm module shall invoke the ReadDataLength opera-
tion (or the respective C-Function) to retrieve the length of the periodicDID. This length
is valid for each ReadData operation till the periodicDID is removed from the scheduler
or updated via a new request. This length shall further be used to check against the
UUDT size.c(RS_Diag_04215)
[SWS_Dcm_01100] Verifications on all sub-functions except stopSending dOn
reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A) with transmission-
Mode different than stopSending, the Dcm shall do the verification for session, security
and mode rule.c(RS_Diag_04215)
[SWS_Dcm_01426] No verifications for sub-function stopSending dOn reception
of the UDS Service ReadDataByPeriodicIdentifier (0x2A) with transmissionMode =
stopSending, the Dcm shall skip the verification for security and mode rule.c(RS_Diag_-
04215)
[SWS_Dcm_01427] Dcm behavior on sub-function stopSending without further
parameters dOn reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A)
with transmissionMode = stopSending and no periodicDataIdentifier in the request, the
Dcm shall stop all scheduled periodicDataIdentifier transmissions.c(RS_Diag_04215)
[SWS_Dcm_01428] Dcm behavior on sub-function stopSending with further pa-
rameters dOn reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A) with
transmissionMode = stopSending and at least one periodicDataIdentifier is in the re-
quest, the Dcm shall stop the scheduled periodic data transmissions for all requested
and in the current session supported periodicDataIdentifiers.c(RS_Diag_04215)
[SWS_Dcm_00716] Serialisation with S/R data interfaces dTo serialize the required
AUTOSAR data types (signed- and unsigned integer) into the response message of
ReadDataByPeriodicIdentifier responses the target endianness configured in DcmD-
spDataEndianness shall be considered for DcmDspData elements having DcmD-
spDataUsePort set to USE_DATA_SENDER_RECEIVER, USE_DATA_SENDER_RE-
CEIVER_AS_SERVICE, USE_ECU_SIGNAL. In case DcmDspDataEndianness is
not present, the DcmDspDataDefaultEndianness shall be used instead.c(RS_-
Diag_04215)
[SWS_Dcm_00843] Ensuring maxim number of periodic DIDs dOn reception of the
UDS Service ReadDataByPeriodicIdentifier (0x2A),the Dcm module shall check if the

162 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

periodicDataIdentifiers requested in a single request do not exceed the configured

DcmDspMaxPeriodicDidToRead (maximum length check). Otherwise (in case the
number of elements is exceeded) the Dcm module shall send a NRC 0x13 (Incorrect
message length or invalid format).c(RS_Diag_04215)
[SWS_Dcm_01094] Behavior on not supported transmissionMode dOn reception
of the UDS Service ReadDataByPeriodicIdentifier(0x2A), the Dcm module shall check
if the transmissionMode is supported, otherwise the Dcm module shall send a NRC
0x31(Request out of range).c(RS_Diag_04215)
Note: With UDS Service ReadDataByPeriodicIdentifier (0x2A), the tester can start one
or more periodicDIDs.
Note: A request of UDS Service ReadDataByPeriodicIdentifier will contain DIDs repre-
sented by only one byte, the low byte of the configured DID. In all cases the complete
DID will be constructed by adding 0xF2 as high byte.
[SWS_Dcm_01095] Verification if periodic DID is supported dOn reception of the
UDS Service ReadDataByPeriodicIdentifier (0x2A), for every requested periodicDIDs,
the Dcm module shall check if the periodicDID is supported (see configuration param-
eter DcmDspDid). If none of the periodicDIDs are supported, the Dcm module shall
send NRC 0x31 (Request out of range).c(RS_Diag_04215)
[SWS_Dcm_01096] Behavior on unused DIDs dIf a DID is set as unused (DcmD-
spDidUsed set to FALSE), the Dcm shall consider the DID as not supported.c(RS_-
Diag_04215)
[SWS_Dcm_00851] Verification for free scheduler slots dOn reception of the
UDS Service ReadDataByPeriodicIdentifier(0x2A) with transmissionMode different than
0x04 "stopSending", the Dcm module shall check if all requested periodicDataIdenti-
fiers not currently in the periodic scheduler can be added to the scheduler considering
the free space of the scheduler (maximum size is defined by configuration parame-
ter DcmDspMaxPeriodicDidScheduler). In case the requested periodicDataIden-
tifiers cannot be added to the scheduler, the Dcm shall send a NRC 0x31 (RequestOut-
OfRange).c(RS_Diag_04215)
Note : To optimize the resource consumption AUTOSAR has chosen a simplified ap-
proach to validate the request message. ISO recommends checking the size only for
currently supported data identifiers.

7.6.2.11.1 Scheduler PeriodicTransmission

Note: The periodic response message layout is according to ISO 14229-1:2013. It

contains the periodic data identifier and the data. The service ID and A_PCI byte is
not part of the periodic response message.
[SWS_Dcm_01101] dThe Dcm shall send all periodic scheduled response by using the
configured DcmDslPeriodicConnections.c(RS_Diag_04215)

163 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Note : Only UUDT messages (IF-PDUs) are supported

ISO 14229-1:2018 defines two distinct scheduler types for ReadDataByPeriodicIdenti-
fier. Depending on the scheduler type, the Dcm has different transmission strategies.
The used scheduler type of the server is selected by setting DcmDspPeriodicTransmis-
sionSchedulerType to one of the two types.
[SWS_Dcm_01568] Support of periodic transmission type 1 dIf DcmDspPerio-
dicTransmissionSchedulerType is set to SCHEDULER_TYPE1 and the Dcm is
set up to send PDIDs, the Dcm shall trigger the transmission of all scheduled PDIDs
each time the configured periodic transmission rate elapses.c(RS_Diag_04215)
[SWS_Dcm_01569] Transmission of one PDID per available connection dIf PDID
transmission is triggered according to [SWS_Dcm_01568], Dcm shall transmit one
PDID per available periodic connection starting with the first PDID in the list of sched-
uled PDIDs.c(RS_Diag_04215)
[SWS_Dcm_01570] Continue in next main function if more PDIDs than available
connections dIf PDID transmission is triggered according to [SWS_Dcm_01568] and
more PDIDs are to transmit than the number of available periodic connections, the
Dcm shall continue the transmission in the next Dcm main function call. Each time the
available periodic connections shall be used.c(RS_Diag_04215)
[SWS_Dcm_01571] Overlapping triggers and transmissions dIf PDID transmission
is triggered according to [SWS_Dcm_01568] or [SWS_Dcm_01572] and the next pe-
riodic transmission rate trigger occurs before the Dcm has finished sending the sched-
uled PDIDs according to [SWS_Dcm_01570], the Dcm shall continue to transmit PDIDs
according to [SWS_Dcm_01570] and schedule the PDIDs of the new trigger after the
last previous PDID has been transmitted.c(RS_Diag_04215)
[SWS_Dcm_01572] Support of periodic transmission type 2 dIf DcmDspPeriod-
icTransmissionSchedulerType is set to SCHEDULER_TYPE2 the Dcm is set up
to send PDIDs and the periodic transmission rate for a scheduler elapses, the Dcm
shall trigger the transmission of the next scheduled PDIDs on all available periodic
connections.c(RS_Diag_04215)
[SWS_Dcm_01573] PDID transmission sequence for scheduler type 2 dFor sched-
uler type 2 transmission of PDIDs within a single elapse of the scheduler, the Dcm shall
start to transmit the first configured PDID and continue to transmit consecutively all
other configured PDIDs. If the last PDID is transmitted, the Dcm restarts the sequence
with the first configured PDID. If a PDID is sent more than once within a single elapse
of the scheduler then the PDIDs contents shall be reloaded with the applicable DID /
Memory data for every re-transmission.c(RS_Diag_04215)
[SWS_Dcm_01574] Continue in next periodic rate scheduler if more PDIDs than
available connections dIf a scheduler type 2 PDID transmission is active according
to [SWS_Dcm_01572] and the number of scheduled PDIDs is larger than the number
of available periodic connections, the Dcm shall continue to send the next scheduled
PDIDs the next time the periodic transmission rate scheduler elapses.c(RS_Diag_-
04215)

164 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

The following example gives an overview about scheduler type 1 and type 2. They use
PDIDs starting at 0xF201 and having all PDID data set to zero. The PDIDs are send
on CAN 2.0, using the CAN-IDs 0x6A0, 0x6A1.
Example 1: Scheduler Type 1
1 SchedulerRate: 1000ms
2
3 PeriodicRate: 4000ms
4
5 NumPeriodicAddr: 1
6
7 NumPDID 2
8
9 1017.02 6A0 01 00 00 00 00 00 00 00
10
11 2016.97 6A0 02 00 00 00 00 00 00 00
12
13
14

15 5016.87 6A0 01 00 00 00 00 00 00 00
16
17 6016.78 6A0 02 00 00 00 00 00 00 00
18
19
20

21 9016.67 6A0 01 00 00 00 00 00 00 00
22
23 10016.63 6A0 02 00 00 00 00 00 00 00
24
25
26

27 13016.52 6A0 01 00 00 00 00 00 00 00
28
29 14016.46 6A0 02 00 00 00 00 00 00 00

Example 2: Scheduler Type 2

1 SchedulerRate: 1000ms
2
3 PeriodicRate: 4000ms
4
5 NumPeriodicAddr: 1
6

7 NumPDID 2
8
9 945.01 6A0 01 00 00 00 00 00 00 00
10
11 4944.78 6A0 02 00 00 00 00 00 00 00
12
13 8944.66 6A0 01 00 00 00 00 00 00 00
14
15 12944.49 6A0 02 00 00 00 00 00 00 00
16
17 16944.33 6A0 01 00 00 00 00 00 00 00
18
19 20944.28 6A0 02 00 00 00 00 00 00 00

165 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

20
21 24944.01 6A0 01 00 00 00 00 00 00 00

Example 3: Aliasing with Scheduler Type 1

1 SchedulerRate: 1000ms
2
3 PeriodicRate: 4000ms
4
5 NumPeriodicAddr: 1
6
7 NumPDID 5
8
9

10 529.89 6A0 01 00 00 00 00 00 00 00
11
12 1529.70 6A0 02 00 00 00 00 00 00 00
13
14 2529.59 6A0 03 00 00 00 00 00 00 00
15

16 3529.35 6A0 04 00 00 00 00 00 00 00
17
18
19
20 4529.16 6A0 05 00 00 00 00 00 00 00 <-- Alias (should start over at
01)
21
22 5529.02 6A0 01 00 00 00 00 00 00 00
23
24 6529.15 6A0 02 00 00 00 00 00 00 00
25

26 7529.03 6A0 03 00 00 00 00 00 00 00
27
28
29
30 8528.92 6A0 04 00 00 00 00 00 00 00 <-- Alias (should start over
at 01)
31
32 9528.82 6A0 05 00 00 00 00 00 00 00
33
34 10528.46 6A0 01 00 00 00 00 00 00 00
35
36 11528.60 6A0 02 00 00 00 00 00 00 00
37
38
39
40 12528.47 6A0 03 00 00 00 00 00 00 00 <-- Alias (should start over
at 01)
41
42 13528.36 6A0 04 00 00 00 00 00 00 00
43
44 14528.27 6A0 05 00 00 00 00 00 00 00

Example 4: Scheduler Type 2

1 SchedulerRate: 1000ms

166 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

2
3 PeriodicRate: 4000ms
4
5 NumPeriodicAddr: 1
6
7 NumPDID 5
8
9
10 592.03 6A0 01 00 00 00 00 00 00 00
11
12 4591.56 6A0 02 00 00 00 00 00 00 00
13
14 8591.13 6A0 03 00 00 00 00 00 00 00
15
16 12590.69 6A0 04 00 00 00 00 00 00 00
17
18 16590.26 6A0 05 00 00 00 00 00 00 00
19
20 20589.78 6A0 01 00 00 00 00 00 00 00
21
22 24589.23 6A0 02 00 00 00 00 00 00 00
23
24 28588.90 6A0 03 00 00 00 00 00 00 00
25
26 32588.45 6A0 04 00 00 00 00 00 00 00
27
28 36588.05 6A0 05 00 00 00 00 00 00 00

Example 5: Scheduler 1 with Multiple Periodic Addresses

1 SchedulerRate: 1000ms
2
3 PeriodicRate: 4000ms
4
5 NumPeriodicAddr: 2
6
7 NumPDID 5
8
9
10
11 778.69 6A0 01 00 00 00 00 00 00 00
12

13 778.73 6A1 02 00 00 00 00 00 00 00
14
15
16
17 1778.56 6A0 03 00 00 00 00 00 00 00
18

19 1778.61 6A1 04 00 00 00 00 00 00 00
20
21
22
23 2778.44 6A0 05 00 00 00 00 00 00 00
24

25
26

167 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

27 4778.24 6A0 01 00 00 00 00 00 00 00
28
29 4778.27 6A1 02 00 00 00 00 00 00 00
30
31
32

33 5778.08 6A0 03 00 00 00 00 00 00 00
34
35 5778.12 6A1 04 00 00 00 00 00 00 00
36
37

38
39 6778.12 6A0 05 00 00 00 00 00 00 00
40
41
42 8777.90 6A0 01 00 00 00 00 00 00 00
43

44 8777.93 6A1 02 00 00 00 00 00 00 00
45
46
47
48 9777.70 6A0 03 00 00 00 00 00 00 00
49

50 9777.73 6A1 04 00 00 00 00 00 00 00
51
52
53
54 10777.57 6A0 05 00 00 00 00 00 00 00

Example 6: Scheduler 2 with Multiple Periodic Addresses

1 SchedulerRate: 1000ms
2
3 PeriodicRate: 4000ms
4
5 NumPeriodicAddr: 2
6

7 NumPDID 5
8
9
10
11

12 764.64 6A0 01 00 00 00 00 00 00 00
13
14 764.69 6A1 02 00 00 00 00 00 00 00
15
16
17

18 4762.79 6A0 03 00 00 00 00 00 00 00
19
20 4762.82 6A1 04 00 00 00 00 00 00 00
21
22
23

24 8762.35 6A0 05 00 00 00 00 00 00 00
25

168 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

26 8762.36 6A1 01 00 00 00 00 00 00 00
27
28
29
30 12762.01 6A0 02 00 00 00 00 00 00 00
31

32 12762.04 6A1 03 00 00 00 00 00 00 00

Example 7: Scheduler 2 with 2 Periodic Addresses and 1 PDID

1 SchedulerRate: 1000ms
2
3 PeriodicRate: 1000ms
4

5 NumPeriodicAddr: 2
6
7 NumPDID 1
8
9
10

11 7.19 6A0 01 00 00 00 00 00 00 00
12
13 77.21 6A1 01 00 00 00 00 00 00 00
14
15

16
17 1077.61 6A0 01 00 00 00 00 00 00 00
18
19 1077.68 6A1 01 00 00 00 00 00 00 00
20
21

22
23 2078.29 6A0 01 00 00 00 00 00 00 00
24
25 2078.40 6A1 01 00 00 00 00 00 00 00
26
27

28
29 3078.26 6A0 01 00 00 00 00 00 00 00
30
31 3078.33 6A1 01 00 00 00 00 00 00 00
32
33

34
35 4079.13 6A0 01 00 00 00 00 00 00 00
36
37 4079.19 6A1 01 00 00 00 00 00 00 00
38

39
40
41 5079.17 6A0 01 00 00 00 00 00 00 00
42
43 5079.24 6A1 01 00 00 00 00 00 00 00
44

45
46

169 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

47 6079.75 6A0 01 00 00 00 00 00 00 00
48
49 6079.82 6A1 01 00 00 00 00 00 00 00
50
51
52

53 7080.77 6A0 01 00 00 00 00 00 00 00
54
55 7080.91 6A1 01 00 00 00 00 00 00 00
56
57

58
59 8080.90 6A0 01 00 00 00 00 00 00 00
60
61 8080.97 6A1 01 00 00 00 00 00 00 00
62
63

64
65 9081.09 6A0 01 00 00 00 00 00 00 00
66
67 9081.15 6A1 01 00 00 00 00 00 00 00

[SWS_Dcm_01103] Require previous confirmation before next transmission dThe

Dcm shall trigger a transmission DcmDslPeriodicTxPduRef only after the DcmD-
slPeriodicTxConfirmationPduId transmit confirmation for the previously trans-
mitted periodic response is received.c(RS_Diag_04215)
[SWS_Dcm_01104] Transmission error behavior dIn case of a PDID transmission
error, the Dcm shall use always the same order of periodicDIDs per client. Transmission
errors shall not influence this order, the Dcm shall continue to retry the transmission
and start the next PDID only after the PDID was transmitted successfully.c(RS_Diag_-
04215)
[SWS_Dcm_01105] No negative response for periodic DID after positive re-
sponse dAfter periodicDIDs are started and a positive response was sent, the Dcm
shall start to send the periodic DID.c(RS_Diag_04215)
[SWS_Dcm_01106] Sending periodic DIDs without further condition checks
dEach time the counter of a periodicDataIdentifiers elapses, the Dcm shall retrieve the
DID data without validating further conditions (i.e. session, security, mode dependen-
cies, ConditionCheckRead and ReadDataLength).c(RS_Diag_04215)
[SWS_Dcm_01107] No periodic DIDs in default session dWhen the diagnostic ses-
sion changes to DefaultSession, the Dcm shall stop all scheduled periodic DIDs.c(RS_-
Diag_04215)
[SWS_Dcm_01108] On session change send only periodic DIDs with allowed se-
curity settings dWhen the diagnostic session changes to a non-defaultSession, any
scheduled periodic DID that was restricted by security access shall be stopped.c(RS_-
Diag_04215)

170 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01109] On session change send only periodic DIDs allowed in the

new session dWhen the diagnostic session changes to a non-defaultSession, any
scheduled periodic DID that is not supported in the new session shall be stopped.c
(RS_Diag_04215)
Note: The rate for a specific transmissionMode is defined as the time between any
two consecutive response messages with the same periodicDataIdentifier, when only
a single periodicDID is scheduled. If multiple periodicDIDs are scheduled concurrently,
the effective period between the same periodicDataIdentifier will vary based upon the
following design parameters:
• The main function recurrence DcmTaskTime
• The number of available periodic connections
• The number of periodicDIDs that can be scheduled concurrently (see configura-
tion parameter DcmDspMaxPeriodicDidScheduler).
[SWS_Dcm_01575] Connection limitation for fast transmission dIf DcmDspPe-
riodicTransmissionMaxPeriodicFastTransmissions is configured, the Dcm
shall limit the number of used periodic connections for transmissionMode ’sendAt-
FastRate’ to DcmDspPeriodicTransmissionMaxPeriodicFastTransmissions
connections.c(RS_Diag_04215)
[SWS_Dcm_01576] Connection limitation for medium transmission dIf DcmD-
spPeriodicTransmissionMaxPeriodicMediumTransmissions is configured,
the Dcm shall limit the number of used periodic connections for transmission-
Mode ’sendAtFastRate’ to DcmDspPeriodicTransmissionMaxPeriodicMedium-
Transmissions connections.c(RS_Diag_04215)
[SWS_Dcm_01577] Connection limitation for slow transmission dIf DcmDspPe-
riodicTransmissionMaxPeriodicSlowTransmissions is configured, the Dcm
shall limit the number of used periodic connections for transmissionMode ’sendAt-
FastRate’ to DcmDspPeriodicTransmissionMaxPeriodicSlowTransmissions
connections.c(RS_Diag_04215)
[SWS_Dcm_01578] Connection order for limited transmissions dIf any of the trans-
mission connection limitations according to [SWS_Dcm_01575], [SWS_Dcm_01576]
or [SWS_Dcm_01577] is configured, the Dcm shall select the DcmDslPeriodic-
Connection in the order of definition. That means that the first transmitted periodic
DID shall take the first configured connections and so forth.c(RS_Diag_04215)
[SWS_Dcm_01110] Periodic DID transmission and security level change dOn any
security level change, the Dcm shall stop any scheduled periodic DID, that was re-
stricted by security access, but not supported by the new security level anymore.c
(RS_Diag_04215)
[SWS_Dcm_01111] Periodic DDDID transmission and session change dIf DcmD-
spDDDIDcheckPerSourceDID is set to TRUE upon a session change, the Dcm shall
stop any scheduled periodic DDDID, that contains source data not supported in the
current session.c(RS_Diag_04215)

171 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01112] Periodic DDDID transmission and security level change dIf

DcmDspDDDIDcheckPerSourceDID is set to TRUE, upon any security level change,
the Dcm shall stop any scheduled periodic DDDID that contains source data not sup-
ported in the current security level.c(RS_Diag_04215)
[SWS_Dcm_01115] Cancel pending read operations dUpon stopping the periodical
read of a data identifier while a pending asynchronous ReadData operation is still in
progress, the Dcm shall cancel the pending read operation by calling ReadData with
OpStatus=DCM_CANCEL.c(RS_Diag_04215)
[SWS_Dcm_01117] Stop cancels pending transmissions dUpon stopping the pe-
riodical read of a data identifier, the Dcm shall cancel pending transmissions of that
DID.c(RS_Diag_04215)
[SWS_Dcm_01118] Finalizing initiated transmissions upon stop dUpon stopping
the periodical read of a data identifier the Dcm shall finalize already initiated transmis-
sions of that DID.c(RS_Diag_04215)

7.6.2.12 Service 0x2C - DynamicallyDefineDataIdentifier

[SWS_Dcm_00259] dThe DSP submodule shall implement the DynamicallyDefine-

DataIdentifier (service 0x2C, diagnostic data access) of the Unified Diagnostic Ser-
vices.c()
The DynamicallyDefineDataIdentifier service is implemented internally in Dcm module.
[SWS_Dcm_00866] dIf DcmDDDIDStorage configuration parameter is set to FALSE,
the Dcm shall initialize all DDDIDs as not present at power-up Dcm_Init).c()
[SWS_Dcm_00867] dIf DcmDDDIDStorage configuration parameter is set to TRUE,
the Dcm shall restore the DDDID definition from NvM at power-up Dcm_Init).c()
[SWS_Dcm_00868] dIf DcmDDDIDStorage configuration parameter is set to
TRUE, the Dcm shall trigger the storage of the DDDID definition to NvRam (via
NvM_SetRamBlockStatus).c()
[SWS_Dcm_00646] dOn reception of service DynamicallyDefineDataIdentifier with
subservice defineByIdentifier or defineByMemoryAddress, the Dcm module shall con-
figure this new DID with associated information receive from the diagnostic request:
Memory address and memory length or DID source, position and size.c()
[SWS_Dcm_00861] dOn reception of the UDS Service DynamicallyDefineDataIden-
tifier (0x2C), the Dcm module shall check if the DDDID will not exceed the config-
ured parameter value DcmDspDDDIDMaxElements. Otherwise (in case the number
of elements will be exceeded) the Dcm module shall send a NRC 0x31 (RequestOut-
OfRange).c()

172 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00854] dOn reception of the UDS Service DynamicallyDefineDataIdenti-

fier (0x2C) with subservice defineByMemoryAddress, the Dcm shall check if the re-
quested AddressAndLengthFormatIdentifier is supported (refer to configura-
tion parameter DcmDspSupportedAddressAndLengthFormatIdentifier), Oth-
erwise the NRC 0x31 (requestOutOfRange) shall be responded. In case the container
AddressAndLengthFormatIdentifier is not present, the Dcm shall accept all
possible AddressAndLengthFormatIdentifiers.c()
[SWS_Dcm_00647] dOn reception of service DynamicallyDefineDataIdentifier with
subservice clearDynamicallyDefinedDataIdentifier, the Dcm module shall remove the
configuration of this DID.c()
[SWS_Dcm_00723] dOn reception of the UDS Service DynamicallyDefineDataIdenti-
fier (0x2C),the Dcm module shall check if the DDDID can be defined in the current
session (see configuration parameter DcmDspDidReadSessionRef). If not, the Dcm
module shall send a NRC 0x31 (RequestOutOfRange).c()
[SWS_Dcm_00724] dOn reception of the UDS Service DynamicallyDefineDataIdenti-
fier (0x2C), the Dcm module shall check if the DDDID can be defined in the current
security level (see configuration parameter DcmDspDidReadSecurityLevelRef). If
not, the Dcm module shall send NRC 0x33 (Security access denied).c()
[SWS_Dcm_00725] dOn reception of the UDS Service DynamicallyDefineDataIdenti-
fier (0x2C), the Dcm module shall check if the requested Source-DIDs are supported in
the current session (see configuration parameter of referenced DID DcmDspDidRead-
SessionRef)). If not, the Dcm module shall send a NRC 0x31 (RequestOutOfRange).c
()
[SWS_Dcm_00726] dOn reception of the UDS Service DynamicallyDefineDataIden-
tifier (0x2C), the Dcm module shall check if the requested Source-DID or the mem-
oryRange are supported in the current security level (see configuration parameter
of referenced DID DcmDspDidReadSecurityLevelRef or memoryRange DcmD-
spReadMemoryRangeSecurityLevelRef). If not, the Dcm module shall send a NRC 0x33
(Security access denied).c()
[SWS_Dcm_00821] dOn reception of the UDS Service DynamicallyDefineDataIdenti-
fier (0x2C), the Dcm module shall check if the requested Source-DID or the memo-
ryRange are supported in the current mode condition (see configuration parameter
of referenced DID DcmDspDidReadModeRuleRef or memoryRange DcmDspRead-
MemoryRangeModeRuleRef). If not, the Dcm module shall send the calculated nega-
tive response code of the referenced DcmModeRule.c()
In case of memory address(es), on reception of ReadDataByIdentifier or Read-
DataByPeriodicIdentifier request for a dynamically defined DID, the Dcm will use the
callout Dcm_ReadMemory for all contained memory addresses to access the data.
[SWS_Dcm_01051] dOn reception of the UDS Service DynamicallyDefineDataIdenti-
fier (0x2C), if the request message contains different MemoryIdValue compare to the
configured values in DcmDspMemoryIdInfo container, the Dcm shall send a NRC 0x31
(RequestOutOfRange).c()

173 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

In case of DID source(s), on reception of ReadDataByIdentifier or ReadDataByPeriod-

icIdentifier request for a dynamically defined DID, the Dcm will use the configuration of
the contained DIDs to read the data.

7.6.2.13 Service 0x2E - WriteDataByIdentifier

[SWS_Dcm_00255] dThe Dcm module shall implement the UDS Service WriteDataByI-
dentifier (0x2E) of the Unified Diagnostic Services.c()
When using Service 0x2E, the request of the tester contains a 2-byte DID and a
dataRecord with the data to be written. The configuration of the Dcm contains a list
of supported DIDs and defines for each configured DID:
• The 2-byte DID (see configuration parameter DcmDspDidIdentifier)
• For every data of the DID:
– The function WriteData to be used for this data (see configuration parame-
ters DcmDspDataWriteFnc and DcmDspDataUsePort)
[SWS_Dcm_01496] Write UDS DID authentication check dOn reception of the UDS
Service WriteDataByIdentifier (0x2E), the Dcm shall check if the write access to the
requested DID is authenticated and write the data identifier only if:
• a DcmDspDidWriteRole is configured for that DID and the verification according
to [SWS_Dcm_01522] was successful or
• the active white list on that connection has for the requested DID one entry with
write access that matches that DID.
c(RS_Diag_04233)
According to [SWS_Dcm_01537] the authentication checks are only executed if
DcmDspAuthentication is configured. In case of a failed authentication the NRC han-
dling is according to [SWS_Dcm_01544] and [SWS_Dcm_01551] applies.
[SWS_Dcm_00467] dOn reception of the UDS Service WriteDataByIdentifier (0x2E),
the Dcm module shall check if the DID is supported (see configuration parameter
DcmDspDid and DcmDspDidRange) If not, the Dcm module shall send NRC 0x31 (Re-
quest out of range) .c()
[SWS_Dcm_00562] dIf a DID is set as unused (DcmDspDidUsed set to FALSE), the
Dcm shall consider the DID as not supported (according to [SWS_Dcm_00467])c()
[SWS_Dcm_00468] dOn reception of the UDS Service WriteDataByIdentifier (0x2E),
the Dcm module shall check if the DID has a Write access configured (see configuration
parameter DcmDspDidWrite in DcmDspDidInfo). If not, the Dcm module shall send
NRC 0x31 (Request out of range).c()

174 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00469] dOn reception of the UDS Service WriteDataByIdentifier (0x2E),

the Dcm module shall check if the DID can be written in the current session (see con-
figuration parameter DcmDspDidWriteSessionRef). If not, the Dcm module shall
send a NRC 0x31 (Request Out of Range).c()
[SWS_Dcm_00470] dOn reception of the UDS Service WriteDataByIdentifier (0x2E),
the Dcm module shall check if the DID can be written in the current security level
(see configuration parameter DcmDspDidWriteSecurityLevelRef). If not, the
Dcm module shall send NRC 0x33 (Security access denied).c()
[SWS_Dcm_00822] dOn reception of the UDS Service WriteDataByIdentifier (0x2E),
the Dcm module shall check if the DID can be written in the current mode condition (see
configuration parameter DcmDspDidWriteModeRuleRef). If not, the Dcm module
shall send the calculated negative response code of the referenced DcmModeRule.c()
[SWS_Dcm_00473] dOn reception of the UDS Service WriteDataByIdentifier (0x2E),
if all signals (DcmDspDidSignal) of the DID have fixed length (DcmDspDataType
is different than UINT8_DYN), the Dcm module shall check if the received data length
corresponds to the DID data length (addition of all DcmDspDataByteSize).c()
[SWS_Dcm_00395] dAfter all verifications (see [SWS_Dcm_00467],
[SWS_Dcm_00468], [SWS_Dcm_00469], [SWS_Dcm_00470], [SWS_Dcm_00473]
) the Dcm module shall write all the signals (DcmDspDidSignal) of the DID by
either calling the configured function DcmDspDataWriteFnc (if parameter DcmD-
spDataUsePort is set to USE_DATA_SYNCH_FNC or USE_DATA_ASYNCH_FNC or
USE_DATA_ASYNCH_FNC_ERROR) or the associated WriteData operations (if param-
eter DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-
DATA_ASYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)
or the associated SenderReceiver interfaces (if parameter DcmDspDataUsePort is
set to USE_DATA_SENDER_RECEIVER or to USE_DATA_SENDER_RECEIVER_AS_-
SERVICE) with the following parameter values:
Data: the dataRecord form the request
DataLength: the number of bytes in the dataRecord (get from the configuration if the
data has fixed length (DcmDspDataType is different than UINT8_DYN) or from the
diagnostic request length if the data has dynamic length (DcmDspDataType is set to
UINT8_DYN)).c()
[SWS_Dcm_01433] dAfter all verifications (see [SWS_Dcm_00467],
[SWS_Dcm_00468], [SWS_Dcm_00469], [SWS_Dcm_00470], [SWS_Dcm_00473] )
for DID’s with DcmDspDidUsePort is set to USE_ATOMIC_SENDER_RECEIVER_-
INTERFACE, USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE or
USE_ATOMIC_NV_DATA_INTERFACE, the Dcm module shall write the data by writing
the associated sender-receiver or NvDataInterface DataServices_{DID}.c()
[SWS_Dcm_00541] dIf the data is configured as a BlockId of the NvRam (parameter
DcmDspDataUsePort set to USE_BLOCK_ID), the Dcm shall :
1) Request NvM_SetBlockLockStatus(<DcmDspDataBlockIdRef>, FALSE), to tem-
porarily unlock the NvM Block (It might be locked by executing this procedure before).

175 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

2) Request NvM_WriteBlock(<DcmDspDataBlockIdRef >, <DataBuffer>) with

BlockId corresponding to the configuration parameter DcmDspDataBlockIdRef)
3) Poll for completion of write request, using NvM_GetErrorStatus()
4a) On success (NVM_REQ_OK), the Dcm shall issue NvM_SetBlockLockStatus(<
DcmDspDataBlockIdRef >, TRUE) (to lock the NvM block against further updates
from the application) and send a positive response message.
4b) Otherwise (on any NvM failure) the Dcm module shall trigger a negative response
with NRC 0x72 (GeneralProgrammingFailure).c()
[SWS_Dcm_CONSTR_6039] Signals with variable datalength dOnly the last signal
(DcmDspDidSignal) of a DID can have variable datalength (DcmDspDataType is set
to UINT8_DYN).c()
In other case the Dcm won’t be able to split the data from the request.
[SWS_Dcm_00639] dTo serialize the request message of UDS Service WriteDataByI-
dentifier request into the required AUTOSAR data types (signed- and unsigned inte-
ger), the target endianness configured in DcmDspDataEndianness shall be consid-
ered for DcmDspData elements having DcmDspDataUsePort set to USE_DATA_-
SENDER_RECEIVER, USE_DATA_SENDER_RECEIVER_AS_SERVICE. In case DcmD-
spDataEndianness is not present, the DcmDspDataDefaultEndianness shall be
used instead.c()
[SWS_Dcm_CONSTR_6018] dDcmDspData elements used in service 0x2E shall not
have DcmDspDataUsePorts set to USE_ECU_SIGNAL.c()
[SWS_Dcm_CONSTR_6073] Dependency for DcmDspDataWriteFnc dDcmDsp-
DataWriteFnc shall be only present if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR
c()
Note: The invocation of functions BndM_WriteStart and BndM_WriteFinalize are not
part of Dcm Specification. The functions are called via project specific implementation
(e.g. CDD).
[SWS_Dcm_01582] Atomic BndM write operation dAfter all verifica-
tions (see [SWS_Dcm_00467], [SWS_Dcm_00468], [SWS_Dcm_00469],
[SWS_Dcm_00470], [SWS_Dcm_00473]) for DIDs with DcmDspDidUsePort is
set to USE_ATOMIC_BNDM, the Dcm module shall write the data by writing the
data to the associated BlockId from the BndM (DcmDspDidBndMBlockIdRef)
using the block specific writing function BndM_WriteBlock_<BlockId.Shortname>.c
(RS_Diag_04243)

176 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01583] Not allowed atomic BndM write operation dIf the Dcm
calls BndM_WriteBlock_’BlockId.Shortname’ according to [SWS_Dcm_01582] and
BndM_WriteBlock_’BlockId.Shortname’ returns E_NOT_OK, the Dcm shall return a
negative response 0x24 (requestSequenceError).c(RS_Diag_04243)
Note: The BndM needs to be set into writing mode as a precondition. This is either
done by the coding sub-module in Dcm or by a CDD.
[SWS_Dcm_01584] Positive response on atomic BndM write operation dIf the
Dcm has triggered an atomic BndM write operation according to [SWS_Dcm_01582],
the Dcm shall return a positive response if the write operation of the BndM has called
Dcm_BndMWriteBlockFinish with the parameter result set to E_OK.c(RS_Diag_04243)
[SWS_Dcm_01585] Negative response on atomic BndM write operation dIf the
Dcm has triggered an atomic BndM write operation according to [SWS_Dcm_01582],
the Dcm shall return a negative response 0x72 (generalProgrammingFailure) if the write
operation of the BndM has called Dcm_BndMWriteBlockFinish with the parameter re-
sult set to E_NOT_OK.c(RS_Diag_04243)
Note: The Dcm needs to ensure that [SWS_Dcm_00024] requirement is respected
while waiting on the job finish callback as specified in [SWS_Dcm_01584] and
[SWS_Dcm_01585].
[SWS_Dcm_01586] dIf the Dcm is reading or writing a DID with DcmDspDidUsePort
set to USE_ATOMIC_BNDM, the Dcm shall transform the dataRecord into the corre-
sponding BndM type. The DID data element structure needs to be compatible to the
referenced ImplementationDataType of the BndMBlockDescriptor. For each DID data
element a corresponding sub-element shall exist in the ImplementationDataType with
the same shortname and the basetypes shall be compatible.c(RS_Diag_04243)
[SWS_Dcm_CONSTR_6099] Consistency of BndM Block configuration dIf a
DcmDspDid has DcmDspDidUsePort set to USE_ATOMIC_BNDM, the parameter
DcmDspDidBndMBlockIdRef shall be present.c()

7.6.2.14 Service 0x2F - InputOutputControlByIdentifier

[SWS_Dcm_00256] dThe Dcm module shall implement the UDS Service InputOutput-
ControlByIdentifier (0x2F).c(RS_Diag_04218)
When using Service 0x2F, the request of the tester contains a 2-byte DID.
The configuration of the Dcm contains a list of supported DID’s. For each DID, the Dcm
configuration specifies:
• The 2-bytes DID (see configuration parameter DcmDspDidIdentifier)
• For every data of the DID :

177 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

– The function Xxx_ReturnControlToECU() for this data (see configuration pa-

rameters DcmDspDataReturnControlToEcuFnc and DcmDspDataUse-
Port)
– The function Xxx_ResetToDefault() for this data (see configuration parame-
ters DcmDspDataResetToDefaultFnc and DcmDspDataUsePort)
– The function Xxx_FreezeCurrentState() for this DID (see configuration pa-
rameters DcmDspDataFreezeCurrentStateFnc and DcmDspDataUse-
Port)
– The function Xxx_ShortTermAdjustment() for this DID (see configura-
tion parameters DcmDspDataShortTermAdjustmentFnc and DcmDsp-
DataUsePort)
– The sizes of the control record used in the function
Xxx_ShortTermAdjustment() (see configuration parameter and DcmD-
spDataByteSize)
[SWS_Dcm_00579] dThe Dcm shall support InputOutputControlParameter definitions
according to Table 7.27.c(RS_Diag_04218)
Hex Description
00 returnControlToECU
01 resetToDefault
02 freezeCurrentState
03 shortTermAdjustment

Table 7.27: InputOutputControlParameter definitions

[SWS_Dcm_01554] IOControl DID authentication check dOn reception of the UDS

Service InputOutputControlByIdentifier (0x2F), the Dcm shall check if the control ac-
cess to the requested DID is authenticated and control the IO only if:
• a DcmDspDidControlRole is configured for that DID and the verification according
to [SWS_Dcm_01522] was successful or
• the active white list on that connection has for the requested DID one entry with
control access that matches that DID.
c(RS_Diag_04218)
According to [SWS_Dcm_01522] the authentication checks are only executed if
DcmDspAuthentication is configured. In case of a failed authentication the NRC
handling is according to [SWS_Dcm_01544] and [SWS_Dcm_01551] applies.
[SWS_Dcm_00563] dOn reception of the UDS Service InputOutputControlByIdentifier
(0x2F), the Dcm module shall check if the DID is supported (see configuration param-
eter DcmDspDid) If not, the Dcm module shall send NRC 0x31 (Request out of range).c
(RS_Diag_04218)

178 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00564] dIf a DID is set as unused (DcmDspDidUsed set to FALSE), the

Dcm shall consider the DID as not supported (according to [SWS_Dcm_00563])c(RS_-
Diag_04218)
[SWS_Dcm_00565] dOn reception of the UDS Service InputOutputControlByIdentifier
(0x2F), the Dcm module shall check if the DID has a Control access configured (see
configuration parameter DcmDspDidControl in DcmDspDidInfo). If not, the Dcm
module shall send NRC 0x31 (Request out of range).c(RS_Diag_04218)
[SWS_Dcm_00566] dOn reception of the UDS Service InputOutputControlByIdentifier
(0x2F), the Dcm module shall check if the DID can be control in the current session (see
configuration parameter DcmDspDidControlSessionRef). If not, the Dcm module
shall send a NRC 0x31 (Request Out of Range).c()
[SWS_Dcm_00567] dOn reception of the UDS Service InputOutputControlByIdentifier
(0x2F), the Dcm module shall check if the DID can be control in the current security
level (see configuration parameter DcmDspDidControlSecurityLevelRef). If not,
the Dcm module shall send NRC 0x33 (Security access denied).c()
[SWS_Dcm_00823] dOn reception of the UDS Service InputOutputControlByIdentifier
(0x2F), the Dcm module shall check if the DID can be control in the current mode
condition (see configuration parameter DcmDspDidControlModeRuleRef). If not,
the Dcm module shall send the calculated negative response code of the referenced
DcmModeRule.c()
[SWS_Dcm_00580] dOn reception of a request for UDS Service InputOutput-
ControlByIdentifier (0x2F) , if all verifications have been successfully done (see
[SWS_Dcm_00563], [SWS_Dcm_00565], [SWS_Dcm_00566], [SWS_Dcm_00567] )
and if the data is configured as a "ECU signal" of the IoHwAb (parameter DcmD-
spDataUsePort), the Dcm shall call the Api IoHwAb_Dcm_<symbolic name of
ECU signal (parameter DcmDspDataEcuSignal)>() with InputOutputControlParam-
eter for the ’action’ parameter and in case of InputOutputControlParameter is set
to ’shortTermAdjustment’ the signal value for the "signal" parameter. In this case
the requirements [SWS_Dcm_00396], [SWS_Dcm_00397], [SWS_Dcm_00398] and
[SWS_Dcm_00399] doesn’t apply.c(RS_Diag_04218)
[SWS_Dcm_00581] dIn case of more than one supported I/O signal per DataIdenti-
fier and the configuration parameter DcmDspDidControlMask is set to DCM_CON-
TROLMASK_INTERNAL, the Dcm shall internally consider the parameter controlEnable-
MaskRecord and control only the included signals in the request message.c(RS_-
Diag_04218)
[SWS_Dcm_CONSTR_6051] dThe configuration parameter DcmDspDidControl-
MaskSize shall be only present if DcmDspDidControlMask is equal to DCM_CON-
TROLMASK_EXTERNAL or DCM_CONTROLMASK_INTERNAL.c()
[SWS_Dcm_01273] dIf the configuration parameter DcmDspDidControlMask is set
to DCM_CONTROLMASK_EXTERNAL or DCM_CONTROLMASK_INTERNAL, or the ele-
ment used in service 0x2F is configured to have an atomic S/R interface, the Dcm

179 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

shall reject requests without included control enable mask record with the NRC 0x13
(incorrectMessageLengthOrInvalidFormat).c(RS_Diag_04218)
[SWS_Dcm_01274] dIf the configuration parameter DcmDspDidControlMask is set
to DCM_CONTROLMASK_NO, the Dcm shall reject request with included control en-
able mask record with the NRC 0x13 (incorrectMessageLengthOrInvalidFormat).c(RS_-
Diag_04218)
[SWS_Dcm_CONSTR_6084] Sender-receiver communication for IOControls is
limited to atomic S/R interfaces dIf a DID has a configured DcmDspDidUsePort
= USE_DATA_ELEMENT_SPECIFIC_INTERFACES, the possible values of DcmDsp-
DataUsePort are limited to non S/R interfaces.c(RS_Diag_04218)
[SWS_Dcm_CONSTR_6085] Atomic S/R for IOControls are limited to non-NV in-
terfaces dIf a DID has a configured DcmDspDidControl, the possible values of
DcmDspDidUsePort are limited to atomic S/R interface and USE_DATA_ELEMENT_-
SPECIFIC_INTERFACES.c(RS_Diag_04218)
[SWS_Dcm_CONSTR_6086] Signals for DIDs with Atomic S/R are not shared
with other DIDs dIf a DcmDspDid is configured to have an atomic S/R interface, all
DcmDspDataElements referenced by this DID shall be referenced only from this DID.
c(RS_Diag_04218)
[SWS_Dcm_CONSTR_6050] dIf a DcmDspDid is used in service 0x2F and is config-
ured to have an atomic S/R interface, the DcmDspDidControlMask shall be set to
DCM_CONTROLMASK_EXTERNAL and the parameter DcmDspDidControlMaskSize
shall be present with a value greater than zero.c()
[SWS_Dcm_00680] Mapping of internal ControlEnableMaskRecord to DID data
elements dIf DcmDspDidControlMask is set to DCM_CONTROLMASK_INTERNAL,the
ControlEnableMaskRecord shall be mapped to the DID data elements by applying the
following mapping :
• The most significant bit of the first byte of the ControlEnableMask shall corre-
spond to the first DID data element
• The second most significant bit of the first byte of the ControlEnableMask shall
correspond to the second DID data element and continuing on in this fashion
utilizing as many ControlEnableMask bytes as necessary to map all DID data
elements.
c(RS_Diag_04218)
The controlEnableMaskRecord is only present, if the DataIdentifer supports more than
one signal.
The Dcm supports atomic S/R interfaces activated by the configuration DcmD-
spDidUsePort set to USE_ATOMIC_SENDER_RECEIVER_INTERFACE or USE_-
ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE. In the text and require-
ments of this chapter the term ’atomic S/R interface’ for IO control means that the
IO controlled DID is configured to one of the two choices.

180 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

The service use case [TPS_SWCT_01654] and the [constr_1679] limits the S/R inter-
faces used for IOControl to explicit S/R communication. In implicit communication is
not supported by the Dcm.
[SWS_Dcm_01434] IOControl General execution sequence dOn reception of a re-
quest for UDS Service InputOutputControlByIdentifier (0x2F) the Dcm shall first exe-
cute the service verifications according to [SWS_Dcm_00563], [SWS_Dcm_00565],
[SWS_Dcm_00566], [SWS_Dcm_00567] and on successful passing the verifications
start the configured service processing.c(RS_Diag_04218)
[SWS_Dcm_00396] dOn reception of a request for UDS Service InputOutputCon-
trolByIdentifier (0x2F) with inputOutputControlParameter equal to returnCon-
trolToEcu, the Dcm module shall invoke all impacted configured function of the
controlEnableMaskRecord (if parameter DcmDspDataUsePort set to USE_DATA_-
SYNCH_FNC or USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_FNC_ERROR; see
configuration parameter DcmDspDataReturnControlToEcuFnc). Alternatively call
all the associated ReturnControlToECU operations (if parameter DcmDspDataUse-
Port set to USE_DATA_SYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_-
SERVER or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR) for every data of the DID
received in the request.c(RS_Diag_04218)
[SWS_Dcm_00397] dOn reception of a request for UDS Service InputOutputCon-
trolByIdentifier (0x2F) with inputOutputControlParameter equal to resetToDe-
fault, the Dcm module shall invoke all impacted configured function of the controlEn-
ableMaskRecord (if parameter DcmDspDataUsePort set to USE_DATA_SYNCH_FNC
or USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_FNC_ERROR; see configuration
parameter DcmDspDataResetToDefaultFnc). Alternatively call all the associated
ResetToDefault operations (if parameter DcmDspDataUsePort set to USE_DATA_-
SYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER or USE_DATA_-
ASYNCH_CLIENT_SERVER_ERROR) for every data of the DID received in the request.c
(RS_Diag_04218)
[SWS_Dcm_00398] dOn reception of a request for UDS Service InputOutputCon-
trolByIdentifier (0x2F) with inputOutputControlParameter equal to freezeCur-
rentState, the Dcm module shall invoke all impacted configured function of the
controlEnableMaskRecord (if parameter DcmDspDataUsePort set to USE_DATA_-
SYNCH_FNC or USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_FNC_ERROR; see
configuration parameter DcmDspDataFreezeCurrentStateFnc). Alternatively call
all the associated FreezeCurrentState operations (if parameter DcmDspDataUse-
Port set to USE_DATA_SYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_-
SERVER or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR) for every data of the DID
received in the request.c(RS_Diag_04218)
[SWS_Dcm_00399] dOn reception of a request for UDS Service InputOutputCon-
trolByIdentifier (0x2F) with inputOutputControlParameter equal to shortTer-
mAdjustment, the Dcm module shall invoke all impacted configured function of

181 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

the controlEnableMaskRecord (if parameter DcmDspDataUsePort set to USE_-

DATA_SYNCH_FNC or USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_FNC_ER-
ROR; see configuration parameter DcmDspDataShortTermAdjustmentFnc). Al-
ternatively call all the associated ShortTermAdjustment operations (if parameter
DcmDspDataUsePort set to USE_DATA_SYNCH_CLIENT_SERVER or USE_DATA_
ASYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)
for every data of the DID received in the request.c(RS_Diag_04218)
[SWS_Dcm_00858] Cancel active IO controls on session change dOn any session
transition, the Dcm shall stop all active IO controls according to [SWS_Dcm_01435]
which are not supported by the new session.c(RS_Diag_04119)
[SWS_Dcm_00628] Cancel active IO controls in default sessions dOn a session
transition to default session, the Dcm shall stop all active IO controls according to
[SWS_Dcm_01435].c(RS_Diag_04119)
[SWS_Dcm_00859] Cancel active IO controls on security level change dOn
any security level change, the Dcm shall stop all active IO controls according to
[SWS_Dcm_01435] which are not support by the new security level anymore.c(RS_-
Diag_04119)
[SWS_Dcm_01435] Dcm cancel IO control sequence dIf the Dcm needs to
cancel an active IO control due to [SWS_Dcm_00858], [SWS_Dcm_00628] or
[SWS_Dcm_00859], the Dcm shall do the following:
• For controlled data elements with DcmDspDataUsePort set to USE_ECU_SIG-
NAL: call to IoHwAb_Dcm_<symbolic ECU signal name>() with ’action’ parameter
set to ReturnControlToECU.
• For controlled data elements with DcmDspDataUsePort set to USE_DATA_-
ASYNCH_CLIENT_SERVER or USE_DATA_SYNCH_CLIENT_SERVER or USE_-
DATA_ASYNCH_CLIENT_SERVER_ERROR: call the C/S interface operation Re-
turnControlToECU.
• For controlled data elements with DcmDspDataUsePort set to USE_DATA_-
SYNCH_FNC or USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_FNC_ERROR:
call the configured function Xxx_ReturnControlToECU (see parameter DcmDsp-
DataReturnControlToEcuFnc)
• For controlled DIDs with is configured atomic S/R interfaces: update the data
element IOOperationRequest with inputOutputControlParameter = 0x00, the
controlEnableMask = 0xFFFFFFFF1 and data element underControl = 0x00.
c(RS_Diag_04119)
[SWS_Dcm_00640] dTo serialize the required AUTOSAR data types (signed- and un-
signed integer) from the request message (in case of inputOutputControlParam-
eter is set to ’shortTermAdjustment’) / into the response message of UDS Service
1
The size of the mask depends on the parameter DcmDspDidControlMaskSize

182 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

InputOutputControlByIdentifier responses, the target endianness configured in DcmD-

spDataEndianness shall be considered for DcmDspData elements having DcmD-
spDataUsePort set to USE_ECU_SIGNAL. In case DcmDspDataEndianness is not
present, the DcmDspDataDefaultEndianness shall be used instead.c(RS_Diag_-
04218)
[SWS_Dcm_00682] dThe controlState in the ControlStatusRecord for positive re-
sponse message of IoControl service shall be retrieved using the associated Read-
Data operation/function/SenderReceiver after application processing on the IO control
request is positively finalized.c(RS_Diag_04218)
Beside the Client/Server interface, the Dcm provides the SenderReceiver interface IO-
ControlRequest_DID. The underControl data element of this interface is calcu-
lated by the Dcm with one state bit for each data element identical to the CEMR. Appli-
cations can directly derive the active control enable status without the need to maintain
internal states.
The bit-mask underControl contains the accumulated status about which data ele-
ments of this particular I/O is currently under diagnostic control. The normal operation
state could be derived if the value of underControl is set to 0x00 (which is the initial
value). Each set bit indicates a data element which is under diagnostic control via
FreezeCurrentState, ’ResetToDefault’ or ’ShortTermAdjustment’.
[SWS_Dcm_01436] Calculation of the underControl data element dThe Dcm shall
calculate the underControl data element of the S/R interface IOControlRe-
quest_DID. The underControl is a bitfield of the same size than the CEMR of the
controlled DID. Each bit represents the same data element as in the CEMR. A value of
0 indicates, that the corresponding data element is currently not controlled by the Dcm,
a value of 1 indicates that it is controlled. The initial value is 0, each control request
for a data element with inputOutputControlParameter equal to ResetToDe-
fault, FreezeCurrentState or ShortTermAdjustment will set the correspond-
ing bit value to 1, and each control request with inputOutputControlParameter
set to ReturnControlToECU will set the bit value to 0.c(RS_Diag_04218)
With each I/O Control request a command IOOperationRequest is provided to the
application to update the input or the respective output. IOOperationRequest con-
tains the inputOutputControlParameter, the controlEnableMask and in case
of ShortTermAdjustment the controlState.
To identify that previous operation has finished (e.g Write IOControlRequest_{DID}),
the user can use the update flag mechanism from the RTE.
The application needs to update their output values and finalizes the request with the
response message IOOperationResponse to the Dcm. The possible values are:
• 0x00 positive response (similar to E_OK)
• 0x10 generalReject
• 0x21 busyRepeatRequest

183 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• 0x22 conditionsNotCorrect
• 0x26 FailurePreventsExecutionOfRequestedAction
• 0x31 requestOutOfRange
• 0x78 ResponsePending (similar to E_PENDING)
Based on the write trigger of the SW-C to IOControlResponse_DID.IOOpera-
tionResponse, the Dcm will:
1. wait for final processing (0x78)
2. send a positive response message (0x00)
3. send a negative response message (all other values, except 0xFF)

Figure 7.11: IO-Control with Sender/Receiver interfaces

[SWS_Dcm_01437] inputOutputControlParameter idle state dThe inputOut-

putControlParameter of data element of IOOperationRequest from S/R inter-
face IOControlRequest_DID shall have an initial value of 0xFF. This value indicates
the application, that the Dcm is currently not processing an UDS service to control this
DID.c(RS_Diag_04218)
[SWS_Dcm_01438] inputOutputControlParameter after processing an UDS
InputOutputControlByIdentifier (0x2F) service dIf the Dcm is processing an In-
putOutputControlByIdentifier request with inputOutputControlParameter equal
to ResetToDefault, FreezeCurrentState or ShortTermAdjustment, the
Dcm shall set the inputOutputControlParameter of data element of IOOpera-
tionRequest from S/R interface IOControlRequest_DID to the idle state 0xFF af-
ter the application has set the IOControlResponse_DID.IOOperationResponse
to 0x00 and before processing other InputOutputControlByIdentifier requests.c(RS_-
Diag_04218)
Upon the Dcm writes IOOperationRequest of IOControlRequest_DID the SWC
processes the IO control request. The SWC informs the Dcm about the current pro-
cessing state by updating IOControlResponse_DID.IOOperationResponse.

184 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01439] Positive response based on IOOperationResponse dIf the

Dcm is processing an InputOutputControlByIdentifier request, it shall reply with a pos-
itive response, if the applications set IOControlResponse_DID.IOOperationRe-
sponse to 0x00.c(RS_Diag_04218)
[SWS_Dcm_01440] Negative response based on IOOperationResponse dIf the
Dcm is processing an InputOutputControlByIdentifier request, it shall reply with a neg-
ative response with the NRC IOControlResponse_DID.IOOperationResponse, if
the applications set IOControlResponse_DID.IOOperationResponse a value dif-
ferent to 0x00 and 0x78.c(RS_Diag_04218)
[SWS_Dcm_01441] RCRRP based on IOOperationResponse dIf the Dcm is pro-
cessing an InputOutputControlByIdentifier request and the IOControlResponse_-
DID.IOOperationResponse has a value of 0x78, the Dcm shall wait until the IO-
ControlResponse_DID.IOOperationResponse gets a value different to 0x78 and
send RCRRP according to [SWS_Dcm_00024].c(RS_Diag_04218)
Note: As shown in figure ??: Sequence diagram for resetToDefault, frezeCurentState
and shortTermAdjustement, the trigger from the SW-C to the Dcm is the explicit S/R
write operation. The use of the RTE functionality ”IsUpdated” is a possible mechanism
for the Dcm to detect a write from SW-C to the S/R data element.
[SWS_Dcm_01275] Common action for all inputOutputControlParameter op-
erations with atomic S/R dIf the Dcm is processing an InputOutputControlByIdentifier
request for a DID configured atomic S/R interface, the Dcm module shall update in the
IOControlRequest_DID the data element IOOperationRequest with
1. controlEnableMask = controlEnableMaskRecord of the request message
2. inputOutputControlParameter = inputOutputControlParameter from the re-
quest message
c(RS_Diag_04218)
The value 0xFF of the inputOutputControlParameter of the command IOOper-
ationRequest is the ’idle’ state. The values 0x00 (ReturnControlToECU), 0x01
(ResetToDefault), 0x02 (FreezeCurrentState) or 0x03 (ShortTermAdjust-
ment) start the request processing and include the control option inputOutputCon-
trolParameter, controlEnableMask and controlState (for ShortTermAd-
justment only).
[SWS_Dcm_01277] Additional action for InputOutputControl operations for
ShortTermAdjustment with atomic S/R dIf the Dcm is processing an InputOutput-
ControlByIdentifier request with inputOutputControlParameter equal to Short-
TermAdjustment for a DID with configured atomic S/R interface, in addition to
[SWS_Dcm_01275] the Dcm module shall update in the IOControlRequest_DID
the data element controlState with content of the controlState from the request
message.c(RS_Diag_04218)

185 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Note: The controlState is a separate data elment that it can be optionally pro-
cessed by a data transformer to transform the byte stream into a composite type (see
Figure 7.11: IO-Control with Sender/Receiver interfaces).
An example of the Dcm S/R interaction is given in Figure 7.12 and Figure 7.13. For
ReturnControlToECU the data from the request is provided to the application, the
Dcm will continue to finalize the request after writing the data into the S/R ports. All
other sub-functions will wait for the application providing the response 0x00 or an code.
sd IOSequence 00

Tester Dcm RTE SWC

2F D001 00 80
Tester requests IOControl
⦁ DID D001
⦁ returnControlToECU
⦁ CEMR 0x80 Write IOControlRequest_{DID}
⦁ underControl = ~CEMR & underControl)

Write IOControlRequest_{DID}.IOOperationRequest
⦁ controlEnableMask = 0x80
⦁ inputOutputControlParameter = 0x00
⦁ Set IsUpdated Flag

alt pos Response

[Read DataServices_{DID}]:
[data = 0x1234]:

6F D001 00 1234
[positive response]:

[Read IOControlRequest_{DID}]:
[underControl]:

[IsUpdatedWriteIOControlRequest_{DID}().IOOper...]:

[status]:

alt check IsUpdated

[Read IOControlRequest_{DID}.IOOperationRequest]:

[Process
IOControlRequest]:
⦁ IOOperationResponse = 0x00
⦁ Set IsUpdated Flag
[Write IOControlResponse_{DID}({Ack|Nack}]:

[Write DataServices_{DID}(data = 0x1234)]:

Figure 7.12: IOSequence 00

186 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

sd IOSequence 01_02_03

2F D001 03 1234 80
Tester requests IOControl
Tester ⦁ DID D001 Dcm RTE SWC
⦁ shortTermAdjustment
⦁ Clear IsUpdated
⦁ CEMR 0x80
[Read IOControlResponse.IOOperationResponse]:
⦁ DidData 0x1234 Write IOControlRequest_{DID}
⦁ controlState = 0x1234 1)

Write IOControlRequest_{DID}.IOOperationRequest
⦁ controlEnableMask = 0x80
⦁ inputOutputControlParameter = 0x03
⦁ Set IsUpdated Flag

[Read IOControlRequest_{DID}]:
[underControl]:

1) controlState is only written for inputOutputControlParameter = 0x03

[IsUpdatedWriteIOControlRequest_{DID}().IOOper...]:
[status]:

alt Check IsUpdated

[True]
[Read IOControlRequest_{DID}.IOOperationRequest]:
[IOOperationRequest.inputOutputControlParameter]:

alt InputOutputControlParameter
[ResetToDefault (01)]

[freezeCurrentState(02)]

[shortTermAcjustment(03)]
[Read IOControlRequest_{DID}]:
[controlState = 0x1234]:

alt OperationStatus

[Pending] [Write IOControlResponse_{DID}({Pending 0x78}]:

⦁ Set IsUpdated Flag

[Done]
[Write IOControlResponse_{DID}({Ack=0x0|Nack}]:

⦁ [Write
Set IsUpdated
DataServices_{DID}(data
Flag = 0x1234)]:

[IsUpdated IOControlResponse]:
[status]:

alt Check IsUpdated [Read IOControlResponse_{DID}]:

[True] [IOOperationResponse ]:

alt IOOperationResponse

[Pending (0x78)]

7F 2F 78 (optional, depending on timing)

[Done (0x00|Nack)] [Update underControl]:

underControl = 0x80 | underControl
[Write IOControlRequest_{DID}.underControl]:
[Read DataServices_{DID}]:
[data = 0x1234]:
6F D001 03 1234

Figure 7.13: IOSequence 01 02 03

[SWS_Dcm_CONSTR_6048] Composite sub elements accessible only by read

dComposite sub elements can only be referred from Read DID i.e. Write and Control
DID are not supported.c()
[SWS_Dcm_CONSTR_6030] dThe ReturnControlToEcu functionnality is existing if
at least one of the following parameters are activated : DcmDspDidFreeze-
CurrentState in ECUC_Dcm_00624 : or DcmDspDidResetToDefault in
ECUC_Dcm_00623 : or DcmDspDidShortTermAdjustment in ECUC_Dcm_00625
: .c()
[SWS_Dcm_CONSTR_6059] Dependency for DcmDspDataFreezeCur-
rentStateFnc dDcmDspDataFreezeCurrentStateFnc shall be only present
if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR
c()

187 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_CONSTR_6063] Dependency for DcmDspDataResetToDefaultFnc

dDcmDspDataResetToDefaultFnc shall be only present if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR
c()
[SWS_Dcm_CONSTR_6064] Dependency for DcmDspDidControlMaskSize d
DcmDspDidControlMaskSize shall be only present if DcmDspDidControlMask is
equal to DCM_CONTROLMASK_EXTERNAL or DCM_CONTROLMASK_INTERNAL.c()
[SWS_Dcm_CONSTR_6081] Dependency for DcmDspDidControlMaskBitPosi-
tion dThe value configured for DcmDspDidControlMaskBitPosition shall be
lower than DcmDspDidControlMaskSize * 8.c()
[SWS_Dcm_CONSTR_6065] Dependency for DcmDspDataReturnControlToE-
cuFnc dDcmDspDataReturnControlToEcuFnc shall be only present if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR
c()
[SWS_Dcm_CONSTR_6066] Dependency for DcmDspDataShortTermAdjust-
mentFnc dDcmDspDataShortTermAdjustmentFnc shall be only present if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR
c()
[SWS_Dcm_CONSTR_6082] Dependency for DcmDspDidControlMaskSize d
DcmDspDidControlMaskSize larger than 4 shall be only allowed if DcmD-
spDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER, USE_DATA_-
ASYNCH_CLIENT_SERVER_ERROR or USE_DATA_SYNCH_CLIENT_SERVER. Note:
ControlEnableMask larger than 32 bits is a very rare use case. Therefore the Dcm
supports only C/S interfaces to solve this use case.c()

7.6.2.15 Service 0x31 - RoutineControl

[SWS_Dcm_00257] dThe Dcm module shall implement the UDS Service RoutineCon-
trol (0x31) for subFunctions startRoutine, stopRoutine and requestsRoutineResults.c
()

188 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

A tester can use UDS Service 0x31 to start, stop or obtain the results of a routine
identified by a 2-byte routineIdentifier. The Dcm module configuration contains a list
of the routineIdentifiers (see configuration parameter DcmDspRoutineIdentifier)
supported by the DCM. For each routineIdentifier, the Dcm configuration specifies:
• The function Xxx_Start() associated with this routineIdentifier (see configuration
parameters DcmDspStartRoutineFnc and DcmDspRoutineUsePort)
• List of signal available in the request and in the response (see configuration pa-
rameters DcmDspStartRoutineIn and DcmDspStartRoutineOut)
• The function Xxx_Stop() associated with this routineIdentifier (see configuration
parameters DcmDspStopRoutineFnc and DcmDspRoutineUsePort)
• List of signal available in the request and in the response (see configuration pa-
rameters DcmDspStopRoutineIn and DcmDspStopRoutineOut)
• The function Xxx_RequestResults() associated with this routineIdentifier (see
configuration parameters DcmDspRequestRoutineResultsFnc and DcmD-
spRoutineUsePort)
• List of signal available in the request and in the response (see configuration
parameters DcmDspRequestRoutineResultsIn and DcmDspRequestRou-
tineResultsOut)
[SWS_Dcm_01442] dIf DcmDspRoutineUsePort is set to true, the Dcm shall call the
corresponding operation of the C/S interfaces RoutineServices_RoutineName to
process this routine.c(RS_Diag_04224)
A routine handler processes the diagnostic routine control request. The Dcm passes the
routineControlOption as input parameters to the routine handler. The routine processes
the request and writes the result to the output parameters of the routine handler call.
In case of shared Rx and Tx buffer, there are two cases where writing to the output
parameters of the routine control can cause overwriting of the input parameters:
• a routine control uses arrays as output parameters (call by reference)
• a routine control writes to output parameters and returns DCM_E_PENDING. It
is called again with DcmOpstatus set to DCM_PENDING. The input parameters
are derived from the Rx buffer that was overwritten by the previous write to the
output parameters
For efficient memory consumption it is controllable, if the Dcm applies further strategies
to separate input and output parameters in those situations.
[SWS_Dcm_01580] Input and output consistency during C/S based routine han-
dling dIf DcmDspRoutineUsePort is set to TRUE and the ClientServerOpera-
tion.diagArgIntegrity of that operation is also set to TRUE, the Dcm shall ensure that
the routine handler in the C/S interfaces RoutineServices_RoutineName writing
to the output parameters will not overwrite the input parameters.c(RS_Diag_04224)

189 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01581] "Routine argument integrity for C/S calls dIf DcmDspRou-

tineUsePort is set to true and DcmDspRoutineInterfaceArgumentIntegrity
is configured, the Dcm shall create the corresponding operation of the C/S interface
RoutineServices_RoutineName with ClientServerOperation.diagArgIntegrity set
to DcmDspRoutineInterfaceArgumentIntegrity.c(RS_Diag_04224)
[SWS_Dcm_CONSTR_6097] Availability of DcmDspRoutineInterfaceArgu-
mentIntegrity dDcmDspRoutineInterfaceArgumentIntegrity shall only be
available if the corresponding DcmDspRoutine has DcmDspRoutineUsePort is set
to true.c()
[SWS_Dcm_01443] dIf DcmDspRoutineUsePort is set to false, the Dcm shall use
the configured callout functions for routine operations.c(RS_Diag_04224)
[SWS_Dcm_00568] dOn reception of the UDS Service RoutineControl (0x31), the Dcm
module shall check if the Routine is supported (see configuration parameter DcmD-
spRoutine) If not, the Dcm module shall send NRC 0x31 (Request out of range).c
()
[SWS_Dcm_00569] dIf a Routine is set as unused (DcmDspRoutineUsed set
to FALSE), the Dcm shall consider the Routine as not supported (according to
[SWS_Dcm_00568])c()
[SWS_Dcm_01555] StartRoutine authentication check dOn reception of the UDS
Service RoutineControl (0x31) with sub-function startRoutine, the Dcm shall check if
the access to the requested routine identifier is authenticated and process the routine
only if:
• a DcmDspStartRoutineRole is configured for that routine and the verification ac-
cording to [SWS_Dcm_01522] was successful or
• the active white list on that connection has one RID entry with sub-function ac-
cess set to startRoutine that matches that service and sub-function.
c(RS_Diag_04233)
[SWS_Dcm_01556] StopRoutine authentication check dOn reception of the UDS
Service RoutineControl (0x31) with sub-function stopRoutine, the Dcm shall check if
the access to the requested routine identifier is authenticated and process the routine
only if:
• a DcmDspStopRoutineRole is configured for that routine and the verification ac-
cording to [SWS_Dcm_01522] was successful or
• the active white list on that connection has one RID entry with sub-function ac-
cess set to stopRoutine that matches that service and sub-function.
c(RS_Diag_04233)
[SWS_Dcm_01557] RequestRoutineResult authentication check dOn reception of
the UDS Service RoutineControl (0x31) with sub-function requestRoutineResult, the

190 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Dcm shall check if the access to the requested routine identifier is authenticated and
process the routine only if:
• a DcmDspRequestRoutineResultsRole is configured for that routine and the ver-
ification according to [SWS_Dcm_01522] was successful or
• the active white list on that connection has one RID entry with sub-function ac-
cess set to requestRoutineResults that matches that service and sub-function.
c(RS_Diag_04233)
According to [SWS_Dcm_01537] the authentication checks are only executed if
DcmDspAuthentication is configured. In case of a failed authentication the NRC
handling is according to [SWS_Dcm_01544] and [SWS_Dcm_01551] applies.
The service RoutineControl (0x31) is of exotic nature and has both, a sub-function and
an identifier. UDS defines a different behavior for this service. Permission checks for
session and security are done on identifier level rather than on sub-function level.
[SWS_Dcm_CONSTR_6100] Same session and security settings for same rou-
tine identifier dAll DcmDspCommonAuthorization that are referenced via DcmD-
spStartRoutineCommonAuthorizationRef, DcmDspStopRoutineCommonAu-
thorizationRef or DcmDspRequestRoutineResultsCommonAuthorization-
Ref from a the same DcmDspRoutine, shall have the same (identical) set of ref-
erenced DcmDspCommonAuthorizationSecurityLevelRef and DcmDspCommo-
nAuthorizationSessionRef.c()
[SWS_Dcm_00570] dOn reception of the UDS Service RoutineControl (0x31), the Dcm
module shall check if the Routine can be executed in the current session (see con-
figuration parameters DcmDspStartRoutineCommonAuthorizationRef, DcmD-
spStopRoutineCommonAuthorizationRef and DcmDspRequestRoutineRe-
sultsCommonAuthorizationRef). If not, the Dcm module shall send a NRC 0x31
(Request Out of Range).c()
[SWS_Dcm_00571] dOn reception of the UDS Service RoutineControl (0x31), the
Dcm module shall check if the Routine can be executed in the current secu-
rity level (see configuration parameter DcmDspStartRoutineCommonAuthoriza-
tionRef, DcmDspStopRoutineCommonAuthorizationRef and DcmDspReque-
stRoutineResultsCommonAuthorizationRef). If not, the Dcm module shall send
NRC 0x33 (Security access denied).c()
[SWS_Dcm_00869] dOn reception of the UDS Service RoutineControl (0x31), the
Dcm module shall check if the SubFunction to the corresponding Routine is supported
(see existence of configuration container DcmDspStopRoutine for SubFunction 0x02;
DcmDspRequestRoutineResults for SubFunction 0x03). If not, the Dcm module
shall send NRC 0x12 (SubFunction not supported).c()
[SWS_Dcm_01169] dOn reception of the UDS Service RoutineControl (0x31) with Sub-
Function startRoutine, the Dcm module shall check if the Routine can be executed in

191 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

the current mode condition (see configuration parameter DcmDspStartRoutineCom-

monAuthorizationRef). If not, the Dcm module shall send the calculated negative
response code of the referenced DcmModeRule.c()
[SWS_Dcm_01170] dOn reception of the UDS Service RoutineControl (0x31) with Sub-
Function stopRoutine, the Dcm module shall check if the Routine can be executed in
the current mode condition (see configuration parameter DcmDspStopRoutineCom-
monAuthorizationRef). If not, the Dcm module shall send the calculated negative
response code of the referenced DcmModeRule.c()
[SWS_Dcm_01171] dOn reception of the UDS Service RoutineControl (0x31) with Sub-
Function requestRoutineResults, the Dcm module shall check if the Routine can be
executed in the current mode condition (see configuration parameter DcmDspReque-
stRoutineResultsCommonAuthorizationRef). If not, the Dcm module shall send
the calculated negative response code of the referenced DcmModeRule.c()
Routines have different input and output parameters depending on the routine con-
figuration (e.g. DcmDspStartRoutineIn for input parameter for the routine start
service). The signature of the called routine operations Xxx_Start, Xxx_Stop and
Xxx_RequestResults is depending on this configuration. The defined parameters for
input and output routine data are optional, and marked in brackets ’[]’ in the definition
in [SWS_Dcm_01203], [SWS_Dcm_01204] and [SWS_Dcm_91013].
[SWS_Dcm_01360] dFor each configured routine input signal in DcmDspStartRou-
tineInSignal, DcmDspStopRoutineInSignal or DcmDspRequestRoutineRe-
sultsInSignal with a signal type unequal to VARIABLE_LENGTH, the optional pa-
rameter ’DcmDspRoutineSignalType dataIn_n’ shall be provided in the corresponding
operations in [SWS_Dcm_01203], [SWS_Dcm_01204] or [SWS_Dcm_91013].c()
[SWS_Dcm_01361] dFor a configured routine input signal in DcmDspStartRou-
tineInSignal, DcmDspStopRoutineInSignal or DcmDspRequestRoutineRe-
sultsInSignal with a signal type equal to VARIABLE_LENGTH the optional pa-
rameter const ’uint8 * dataInVar’ shall be provided in the corresponding operations in
[SWS_Dcm_01203] [SWS_Dcm_01204] or [SWS_Dcm_91013].c()
[SWS_Dcm_01362] dFor each configured routine output signal in DcmDsp-
StartRoutineOutSignal, DcmDspStopRoutineOutSignal or DcmDspReque-
stRoutineResultsOutSignal with a signal type unequal to VARIABLE_LENGTH
the optional parameter ’DcmDspRoutineSignalType dataOut_n’ shall be provided
in the corresponding operations in [SWS_Dcm_01203], [SWS_Dcm_01204] or
[SWS_Dcm_91013].c()
[SWS_Dcm_01363] dFor a configured routine output signal in DcmDspStartRouti-
neOutSignal, DcmDspStopRoutineOutSignal or DcmDspRequestRoutineRe-
sultsOutSignal with a signal type equal to VARIABLE_LENGTH the optional pa-
rameter const ’uint8 * dataOutVar’ shall be provided in the corresponding operations in
[SWS_Dcm_01203], [SWS_Dcm_01204] or [SWS_Dcm_91013].c()
[SWS_Dcm_01364] dThe optional in/out parameter currentDataLength in
[SWS_Dcm_01203], [SWS_Dcm_01204] or [SWS_Dcm_91013] is always present if

192 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

at least one of the routine input signal data or routine output signal data have a signal
with routine type ’VARIABLE_LENGTH’.c()
Note: The ’currentDataLength’ parameter as in/out parameter contains the data length
in bytes of the ’dataInVar’ while calling the operation and it returns the length in bytes
of the ’dataOutVar’. As ’dataInVar’ and ’dataOutVar’ are optional, ’currentDataLength’
is only present if at least one of this optional parameter is used.
[SWS_Dcm_00590] dWhen receiving a request for UDS Service RoutineControl
(0x31) if all verifications have been successfully done (see [SWS_Dcm_00568],
[SWS_Dcm_00570], [SWS_Dcm_00571]), the Dcm module shall split the routineCon-
trolOptionRecord received according of the list of input signal configured for this routine
( see configuration parameters DcmDspStartRoutineIn, DcmDspStopRoutineIn,
DcmDspRequestRoutineResultsIn)c()
[SWS_Dcm_00400] dWhen receiving a request for UDS Service RoutineControl (0x31)
with subfunction startRoutine, if all verifications have been successfully done (see
[SWS_Dcm_00568], [SWS_Dcm_00570], [SWS_Dcm_00571]), the Dcm module shall
call the configured Xxx_Start() function passing the dataIn, calculated from routineCon-
trolOptionRecord (see [SWS_Dcm_00590]), and the dataOut reference according of
the list of output signal configured for this routine ( see configuration parameter DcmD-
spStartRoutineOut).c()
[SWS_Dcm_00401] dUpon completing [SWS_Dcm_00400], when Xxx_Start() returns
E_OK, the Dcm module shall reply with a positive response with the data returned
by Xxx_Start() in the dataOut as routineStatusRecord (dataOut are merged according
to the list of output signal configured for this routine ( see configuration parameter
DcmDspStartRoutineOut)).c()
[SWS_Dcm_00402] dWhen receiving a request for UDS Service RoutineControl (0x31)
with subfunction stopRoutine, if all verifications have been successfully done (see
[SWS_Dcm_00568], [SWS_Dcm_00570], [SWS_Dcm_00571]), the Dcm module shall
call the configured Xxx_Stop() function passing the dataIn, calculated from routineCon-
trolOptionRecord (see [SWS_Dcm_00590]), and the dataOut reference according of
the list of output signal configured for this routine ( see configuration parameter DcmD-
spStopRoutineOut).c()
[SWS_Dcm_00403] dUpon completing [SWS_Dcm_00402], when Xxx_Stop() returns
E_OK, the Dcm module shall reply with a positive response with the data returned
by Xxx_Stop()in the dataOut as routineStatusRecord (dataOut are merged according
to the list of output signal configured for this routine ( see configuration parameter
DcmDspStopRoutineOut)).c()
[SWS_Dcm_00404] dWhen receiving a request for UDS Service RoutineControl (0x31)
with subfunction requestRoutineResults, if all verifications have been successfully done
(see [SWS_Dcm_00568], [SWS_Dcm_00570], [SWS_Dcm_00571]), the Dcm module
shall call the configured Xxx_RequestResults() function passing the dataIn, calculated
from routineControlOptionRecord (see [SWS_Dcm_00590])and provide the dataOut

193 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

reference according of the list of output signal configured for this routine ( see configu-
ration parameter DcmDspRequestRoutineResultsOut).c()
[SWS_Dcm_00405] dUpon completing [SWS_Dcm_00404], when
Xxx_RequestResults() returns E_OK, the Dcm module shall reply with a positive
response with the data returned by Xxx_RequestResults()in the dataOut as routineS-
tatusRecord (dataOut are merged according to the list of output signal configured for
this routine ( see configuration parameter DcmDspRequestRoutineResultsOut)).c
()
[SWS_Dcm_00641] dTo serialize the required AUTOSAR data types (signed- and un-
signed integer) from the request message / into the response message of UDS Service
RoutineControl, the target endianness configured in DcmDspRoutineSignalEndi-
anness shall be considered for DcmDspRoutine signals having set to fixed length (
DcmDspRoutineSignalType set to other value than VARIABLE_LENGTH).c()
[SWS_Dcm_CONSTR_6072] Dependency for DcmDspRoutineSignalEndian-
ness dIn case DcmDspRoutineSignalEndianness is not present, the DcmDsp-
DataDefaultEndianness shall be used instead.c()
[SWS_Dcm_01139] dThe Dcm shall follow the NRC handling for RoutineControlService
according to ISO 14229-1 [1].c()
[SWS_Dcm_01140] dOn reception of the UDS Service RoutineControl (0x31), the Dcm
module shall check the overall length of the request. If length of the request is wrong,
the Dcm module shall send NRC 0x13 (Incorrect message length or invalid format) to
the tester.c()
[SWS_Dcm_01141] dThe Dcm shall call the appropriate routine functions of the SWC
after having performed the total length check and the Mode rules, security level
and session checks (DcmDspStartRoutineCommonAuthorizationRef, DcmD-
spStopRoutineCommonAuthorizationRef and DcmDspRequestRoutineRe-
sultsCommonAuthorizationRef).c()
Note: Subsequent checks have to be performed by the SWC.
[SWS_Dcm_01194] dOn reception of the UDS Service RoutineControl (0x31), for every
requested RID inside the OBD range (E000-E0FF), the Dcm shall implicitly allow sub-
function StartRoutine.c()
[SWS_Dcm_00701] dOn reception of the UDS Service RoutineControl (0x31), for every
requested RID inside the OBD range (E000-E0FF) and usage of UDS interface, the Dcm
module shall use the routineInfo byte value from DcmDspRoutineInfoByte in the
response to the tester.c()
[SWS_Dcm_01330] dIf DcmDspEnableObdMirror is set to true, an explicitly config-
ured RID inside the OBD range (E000-E0FF) shall use the UDS interface.c()
[SWS_Dcm_01331] dIf DcmDspEnableObdMirror is set to false, all requests within
the OBD RID range shall use the UDS interface.c()

194 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01332] dOn reception of the UDS Service RoutineControl (0x31), for every
requested RID inside the OBD range (E000-E0FF), the Dcm module shall handle the
RID as defined for OBD Service $08 (see [SWS_Dcm_00418], [SWS_Dcm_00947],
[SWS_Dcm_00419], [SWS_Dcm_00420], [SWS_Dcm_00948], [SWS_Dcm_01192]) if
DcmDspEnableObdMirror is set to true and RID not explicitly configured.c()
[SWS_Dcm_01333] dOn reception of the UDS Service RoutineControl (0x31), for every
requested RID inside the OBD range (E000-E0FF) and usage of OBD interface, the Dcm
shall use the routineInfo byte value from DcmDspRequestControlInfoByte in the
response to the tester.c()
If DcmDspEnableObdMirror is set to FALSE or the RID is explicitly configured inside
the OBD TestId range (E000-E0FF), the access to the OBD data shall be given in the
following way:
[SWS_Dcm_01390] dOn reception of an UDS Service RoutineControl (0x31) request
with one or more ”availability OBDTestIds” as parameter, the Dcm module shall respond
with the corresponding supported (=configured) RIDs.c()
[SWS_Dcm_01391] dOn reception of an UDS Service RoutineControl (0x31) request
”availability OBDTestIds” together with other OBDTestIds as parameter, the Dcm mod-
ule shall ignore the request.c()
[SWS_Dcm_01392] dOn reception of an UDS Service RoutineControl (0x31) request
with a OBDTestIds that is not an ”availability OBDTestIds”, the Dcm module shall invoke
the configured Xxx_Start() function.c()
[SWS_Dcm_01393] dAs specified in [3, SAE J1979], unused data bytes shall be filled
with $00.c()
[SWS_Dcm_01394] dIf Xxx_Start() doesn’t return E_OK, the Dcm shall return NRC
0x22.c()
[SWS_Dcm_00668] dIf the operation Start() returns value E_NOT_OK, the Dcm mod-
ule shall send a negative response with NRC code equal to ErrorCode parameter
value.c()
[SWS_Dcm_00669] dIf the operation Start() returns value DCM_E_FORCE_RCRRP,
the Dcm module shall start the transmission of NRC 0x78.c(RS_Diag_04249)
[SWS_Dcm_00670] dIf the operation Stop() returns value E_NOT_OK, the Dcm mod-
ule shall send a negative response with NRC code equal to ErrorCode parameter
value.c()
[SWS_Dcm_00671] dIf the operation Stop() returns value DCM_E_FORCE_RCRRP,
the Dcm module shall start the transmission of NRC 0x78.c(RS_Diag_04249)
[SWS_Dcm_00672] dIf the operation RequestResults() returns value E_NOT_OK, the
Dcm module shall send a negative response with NRC code equal to ErrorCode param-
eter value.c()

195 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00673] dIf the operation RequestResults () returns value

DCM_E_FORCE_RCRRP, the Dcm module shall start the transmission of NRC
0x78.c(RS_Diag_04249)
[SWS_Dcm_CONSTR_6071] Dependency for DcmDspStartRoutineFnc, DcmD-
spStopRoutineFnc, DcmDspRequestRoutineResultsFnc, DcmDspStartRou-
tineConfirmationFnc, DcmDspStopRoutineConfirmationFnc dThe following
configuration parameters shall only be present if DcmDspRoutineUsePort is set to
FALSE.
• DcmDspStartRoutineFnc
• DcmDspStopRoutineFnc
• DcmDspRequestRoutineResultsFnc
• DcmDspStartRoutineConfirmationFnc
• DcmDspStopRoutineConfirmationFnc
c()

7.6.2.16 Service 0x3E - Tester Present

[SWS_Dcm_00251] dThe Dcm module shall implement the Tester Present (service
0x3E, diagnostic communication and security) of the Unified Diagnostic Services for
the subfunction values 0x00 and 0x80.c()
[SWS_Dcm_01558] Skipping authentication check for tester present dThe Dcm
shall process the UDS service 0x3E (TesterPresent) independently from the current
authentication state.c(RS_Diag_04230)
This service is used to keep one or multiple servers in a diagnostic session being
different than the defaultSession.

7.6.2.17 Service 0x3D - WriteMemoryByAddress

[SWS_Dcm_00488] dThe Dcm module shall implement the WriteMemoryByAddress

(service 0x3D) of the Unified Diagnostic Services.c()
This service is used to write data using a physical memory address.
[SWS_Dcm_00855] dOn reception of the UDS Service WriteMemoryByAddress
(0x3D), the Dcm shall check if the requested AddressAndLengthFormatIdenti-
fier is supported (refer to configuration parameter DcmDspSupportedAddressAn-
dLengthFormatIdentifier), Otherwise the NRC 0x31 (requestOutOfRange) shall
be responded. In case the container AddressAndLengthFormatIdentifier is
not present, the Dcm shall accept all possible AddressAndLengthFormatIdentifiers.c()

196 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00489] dOn reception of the UDS Service WriteMemoryByAddress

(0x3D), the Dcm shall check if the complete memory range to write to (from ’mem-
oryAddress’ parameter to ’memoryAddress + memorySize -1’) is inside the allowed
memory ranges (check of DcmDspWriteMemoryRangeLow and DcmDspWriteMem-
oryRangeHigh parameters for each DcmDspWriteMemoryRangeInfo container
or DcmDspWriteMemoryRangeByLabelLow and DcmDspWriteMemoryRangeBy-
LabelHigh parameters for each DcmDspWriteMemoryRangeByLabelInfo con-
tainer). If not, the Dcm module shall send NRC 0x31 (Request out of range).c()
[SWS_Dcm_00490] dOn reception of the UDS Service WriteMemoryByAddress
(0x3D), the Dcm shall check if the complete memory range (from ’memoryAddress’
parameter to ’memoryAddress + memorySize -1’) can be written in the current secu-
rity level (see DcmDspWriteMemoryRangeSecurityLevelRef). If security level is not
correct, the Dcm module shall send NRC 0x33 (securityAccessDenied).c()
[SWS_Dcm_00825] dOn reception of the UDS Service WriteMemoryByAddress
(0x3D), the Dcm shall check if the complete memory range (from ’memoryAddress’
parameter to ’memoryAddress + memorySize -1’) can be written in the current mode
condition (see DcmDspWriteMemoryRangeModeRuleRef). If mode condition is not
correct, the Dcm module shall send the calculated negative response code of the refer-
enced dcmModeRule.c()
[SWS_Dcm_00491] dOn reception of the UDS Service WriteMemoryByAddress
(0x3D), and after verification of the validity of the request (see [SWS_Dcm_00489]
and [SWS_Dcm_00490]) the Dcm module shall call the callout Dcm_WriteMemory.c()
[SWS_Dcm_01052] dOn reception of the UDS Service WriteMemoryByAddress
(0x3D), if the request message contains different MemoryIdValue compare to the con-
figured values in DcmDspMemoryIdInfo container, the Dcm shall send a NRC 0x31
(RequestOutOfRange).c()
[SWS_Dcm_01056] dThe configured ranges of memory address (DcmDspReadMemo-
ryRangeHigh and DcmDspReadMemoryRangeLow or DcmDspReadMemoryRange-
ByLabelHigh and DcmDspReadMemoryRangeByLabelLow) shall not overlap each
other.c()
[SWS_Dcm_01358] dOn reception of the UDS Service WriteMemoryByAddress
(0x3D), the Dcm shall check if the complete memory range (from ’memoryAddress’
parameter to ’memoryAddress + memorySize -1’) can be written in the current session
(see DcmDspWriteMemoryRangeSessionLevelRef). If the session is not correct, the
Dcm module shall send NRC 0x31 (RequestOutOfRange).c()
[SWS_Dcm_00643] dIf the operation Dcm_WriteMemory returns
DCM_WRITE_FAILED, the Dcm module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.c()
[SWS_Dcm_00837] dIf the call to Dcm_WriteMemory returns
DCM_WRITE_FORCE_RCRRP, the Dcm shall invoke the transmit request for
RCR-RP (NRC 0x78 transmission) and the Dcm shall not realize further invocation of
the operation till RCR-RP is transmitted.c(RS_Diag_04249)

197 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00838] dAfter transmit confirmation of a RCR-RP transmitted on the con-

text of [SWS_Dcm_00837], the Dcm calls, from Dcm_MainFunction (due to call con-
text), Dcm_WriteMemory again with OpStatus = DCM_FORCE_RCRRP_OK.c()

7.6.2.18 Service 0x23 - ReadMemoryByAddress

This service is used to read data using a physical memory address.

[SWS_Dcm_00492] dThe Dcm module shall implement the ReadMemoryByAddress
(service 0x23) of the Unified Diagnostic Services.c()
[SWS_Dcm_00853] dOn reception of the UDS Service ReadMemoryByAddress
(0x23), the Dcm shall check if the requested AddressAndLengthFormatIdenti-
fier is supported (refer to configuration parameter DcmDspSupportedAddressAn-
dLengthFormatIdentifier), Otherwise the NRC 0x31 (requestOutOfRange) shall
be responded. In case the container DcmDspAddressAndLengthFormatIdenti-
fier is not present, the Dcm shall accept all possible AddressAndLengthFormatIden-
tifiers. ).c()
[SWS_Dcm_00493] dOn reception of the UDS Service ReadMemoryByAddress
(0x23), the Dcm shall check if the complete memory range to read from (from
’memoryAddress’ parameter to ’memoryAddress + memorySize -1’) is inside the al-
lowed memory ranges (check of DcmDspReadMemoryRangeLow and DcmDspRead-
MemoryRangeHigh parameters for each DcmDspReadMemoryRangeInfo container
or DcmDspReadMemoryRangeByLabelLow and DcmDspReadMemoryRangeByLa-
belHigh parameters for each DcmDspReadMemoryRangeByLabelInfo container).
If not, the Dcm module shall send NRC 0x31 (Request out of range).c()
[SWS_Dcm_00494] dOn reception of the UDS Service ReadMemoryByAddress
(0x23), the Dcm shall check if the complete memory range (from ’memoryAddress’
parameter to ’memoryAddress + memorySize -1’) can be readen in the current secu-
rity level (see DcmDspReadMemoryRangeSecurityLevelRef). If security level is not
correct, the Dcm module shall send NRC 0x33 (securityAccessDenied).c()
[SWS_Dcm_00826] dOn reception of the UDS Service ReadMemoryByAddress
(0x23), the Dcm shall check if the complete memory range (from ’memoryAddress’
parameter to ’memoryAddress + memorySize -1’) can be readen in the current mode
condition (see DcmDspReadMemoryRangeModeRuleRef). If mode condition is not
correct, the Dcm module shall send calclulated negative response code of the refer-
enced DcmModeRule.c()
[SWS_Dcm_00495] dOn reception of the UDS Service ReadMemoryByAddress
(0x23), and after verification of the validity of the request (see [SWS_Dcm_00493]
and [SWS_Dcm_00494]) the Dcm module shall call the callout Dcm_ReadMemory.c()

198 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01053] dOn reception of the UDS Service ReadMemoryByAddress

(0x23), if the request message contains different MemoryIdValue compare to the con-
figured values in DcmDspMemoryIdInfo container, the Dcm shall send a NRC 0x31
(RequestOutOfRange).c()
[SWS_Dcm_01158] dThe configured ranges of memory address (DcmDspReadMemo-
ryRangeHigh and DcmDspReadMemoryRangeLow or DcmDspReadMemoryRange-
ByLabelHigh and DcmDspReadMemoryRangeByLabelLow) shall not overlap each
other.c()
[SWS_Dcm_01359] dOn reception of the UDS Service ReadMemoryByAddress
(0x23), the Dcm shall check if the complete memory range (from ’memoryAddress’
parameter to ’memoryAddress + memorySize -1’) can be read in the current session
(see DcmDspReadMemoryRangeSessionLevelRef). If the session is not correct, the
Dcm module shall send NRC 0x31 (RequestOutOfRange).c()
[SWS_Dcm_00644] dIf the operation Dcm_ReadMemory returns
DCM_READ_FAILED, the Dcm module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.c()
[SWS_Dcm_00839] dIf the call to Dcm_ReadMemory returns
DCM_READ_FORCE_RCRRP, the Dcm shall invoke the transmit request for RCR-RP
(NRC 0x78 transmission) and the Dcm shall not realize further invocation of the
operation till RCR-RP is transmitted.c(RS_Diag_04249)
[SWS_Dcm_00840] dAfter transmit confirmation of a RCR-RP transmitted on the con-
text of [SWS_Dcm_00839], the Dcm calls, from Dcm_MainFunction (due to call con-
text), Dcm_ReadMemory again with OpStatus = DCM_FORCE_RCRRP_OK.c()

7.6.2.19 Service 0x34 - RequestDownload

This service is used to request the start of a download process.

[SWS_Dcm_00496] dThe Dcm module shall implement the RequestDownload (service
0x34) of the Unified Diagnostic Services.c(RS_Diag_04033)
[SWS_Dcm_00856] dOn reception of the UDS ServiceRequestDownload (0x34), the
Dcm shall check if the requested AddressAndLengthFormatIdentifier is sup-
ported (refer to configuration parameter DcmDspSupportedAddressAndLength-
FormatIdentifier), Otherwise the NRC 0x31 (requestOutOfRange) shall be re-
sponded. In case the container AddressAndLengthFormatIdentifier is not
present, the Dcm shall accept all possible AddressAndLengthFormatIdentifiers.c()
[SWS_Dcm_01057] dOn reception of the UDS ServiceRequestDownload (0x34), if the
request message contains different MemoryIdValue compare to the configured values
in DcmDspMemoryIdInfo container, the Dcm shall send a NRC 0x31 (RequestOut-
OfRange).c()

199 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01132] dNRC described in Table 7.28 shall be the responsibility of the

callout function.c()
NRC Use Case
0x31 requestOutOfRange The specified dataFormatIdentifier is not valid.
0x70 uploadDownload- An attempt to download to a server’s memory cannot be
NotAccepted accomplished due to some fault conditions.
Note: this NRC will be handled by the callout only if mode rule is
not used for this case

Table 7.28: NRC managed by callout function for service 0x34

Note: the callout function can, if needed, return also other NRC but the ones above
won’t be treated by the Dcm module.
[SWS_Dcm_00757] dIf the operation Xxx_ProcessRequestDownload returns value
E_NOT_OK, the Dcm module shall send a negative response with NRC code equal to
the parameter ErrorCode parameter value.c()
[SWS_Dcm_01417] dUpon calling Xxx_ProcessRequestDownload, the Dcm shall
write the maximum possible buffer size into the BlockLength parameter.c(RS_Diag_-
04033)
[SWS_Dcm_01418] dIf the function call Xxx_ProcessRequestDownload returns a
requested buffer length larger than the supported buffer length of the current proto-
col connection, the Dcm shall report the Det error DCM_E_INTERFACE_BUFFER_-
OVERFLOW.c(RS_Diag_04033) For definition of DCM_E_INTERFACE_BUFFER_OVER-
FLOW see [SWS_Dcm_00040].
[SWS_Dcm_01419] dIf the function call Xxx_ProcessRequestDownload returns a
requested buffer length smaller or equal than the supported buffer length of the current
protocol connection, the Dcm shall return the BlockLength value within the maxNum-
berOfBlockLength parameter of the positive response.c(RS_Diag_04033)

7.6.2.20 Service 0x35 - RequestUpload

This service is used to request the start of a upload process.

[SWS_Dcm_00499] dThe Dcm module shall implement the RequestUpload (service
0x35) of the Unified Diagnostic Services.c(RS_Diag_04033)
[SWS_Dcm_00857] dOn reception of the UDS RequestUpload (0x35), the Dcm shall
check if the requested AddressAndLengthFormatIdentifier is supported (refer
to configuration parameter DcmDspSupportedAddressAndLengthFormatIden-
tifier), Otherwise the NRC 0x31 (requestOutOfRange) shall be responded. In case
the container AddressAndLengthFormatIdentifier is not present, the Dcm shall
accept all possible AddressAndLengthFormatIdentifiers.c()

200 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01055] dOn reception of the UDS RequestUpload (0x35), if the request

message contains different MemoryIdValue compare to the configured values in DcmD-
spMemoryIdInfo container, the Dcm shall send a NRC 0x31 (RequestOutOfRange).c
()
[SWS_Dcm_01133] dNRC described in Table 7.29 shall be the responsibility of the
callout function.c()
NRC Use Case
0x31 - requestOut- The specified dataFormatIdentifier is not valid.
OfRange
0x70 - uploadDownload- An attempt to download to a server’s memory cannot be
NotAccepted accomplished due to some fault conditions.
Note: this NRC will be handled by the callout only if mode rule is
not used for this case

Table 7.29: NRC managed by callout function for service 0x35

Note: the callout function can, if needed, return also other NRC but the ones above
won’t be treated by the Dcm module.
[SWS_Dcm_00758] dIf the operation Xxx_ProcessRequestUpload returns value
E_NOT_OK, the Dcm module shall send a negative response with NRC code equal to
the parameter ErrorCode parameter value.c()
[SWS_Dcm_01420] dUpon calling Xxx_ProcessRequestUpload, the Dcm shall
write the maximum possible buffer size into the BlockLength parameter.c(RS_Diag_-
04033)
[SWS_Dcm_01421] dIf the function call Xxx_ProcessRequestUpload returns a re-
quested buffer length larger than the supported buffer length of the current protocol
connection, the Dcm shall report the Det error DCM_E_INTERFACE_BUFFER_OVER-
FLOW.c(RS_Diag_04033) For definition of DCM_E_INTERFACE_BUFFER_OVERFLOW
see [SWS_Dcm_00040].
[SWS_Dcm_01422] dIf the function call Xxx_ProcessRequestUpload returns a re-
quested buffer length smaller or equal than the supported buffer length of the current
protocol connection, the Dcm shall return the BlockLength value within the maxNum-
berOfBlockLength parameter of the positive response.c(RS_Diag_04033)

7.6.2.21 Service 0x36 - TransferData

This service is used to transfer data during a download or upload process.

[SWS_Dcm_00502] dThe Dcm module shall implement the TransferData (service
0x36) of the Unified Diagnostic Services.c(RS_Diag_04033)
[SWS_Dcm_00503] dOn reception of the UDS Service TransferData (0x36), if a down-
load process is running (RequestDownload service has been previously received)

201 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

and the request format is correct, the Dcm module shall call the callout Xxx_Pro-
cessTransferDataWrite.c(RS_Diag_04033)
[SWS_Dcm_00504] dOn reception of the UDS Service TransferData (0x36), if an up-
load process is running (RequestUpload service has been previously received) and the
request format is correct, the Dcm module shall call the callout Xxx_ProcessTrans-
ferDataRead.c(RS_Diag_04033)
[SWS_Dcm_00645] dOn reception of the UDS Service TransferData (0x36), if a block
sequence error is detected, the Dcm module shall trigger a negative response with NRC
0x73 (WrongBlockSequenceCounter)c()
[SWS_Dcm_01444] dOn reception of the UDS Service TransferData (0x36), if a file
download is running (RequestFileTransfer service has been previously received with
0x01 (AddFile) or 0x03 (ReplaceFile)) and the request format is correct, the Dcm mod-
ule shall call the callout Dcm_WriteFile().c()
[SWS_Dcm_01445] dOn reception of the UDS Service TransferData (0x36), if a file
or directory information upload is running (RequestFileTransfer service has been pre-
viously received with 0x04 (ReadFile) or 0x05 (ReadDir)) and the request format is
correct, the Dcm module shall call the callout Dcm_ReadFileOrDir().c()
[SWS_Dcm_01173] dNRCs described in Table 7.30 shall be the responsibility of the
callout function.c()
NRC Use Case
0x24 - requestSequenceError only for the following conditions:
If the RequestDownload or RequestUpload service
is active, but the server has already received all
data as determined by the memorySize parameter
in the active RequestDownload or RequestUpload
service
0x31 - requestOutOfRange Only for the following conditions:
The transferRequestParameterRecord contains
additional control parameters (e.g. additional
address information) and this control information is
invalid. The transferRequestParameterRecord is
not consistent with the server’s memory alignment
constraints
0x71 - transferDataSuspended The data transfer operation was halted due to
some fault.
0x72 - generalProgrammingFailure If the server detects an error when finalizing the
data transfer between the client and server (e.g.,
via an integrity check).
0x92 - voltageTooHigh The voltage measured is higher than the maximum
acceptable voltage for downloading data.
0x93 - voltageTooLow The voltage measured is under the minimum
acceptable voltage for downloading data.

Table 7.30: NRC managed by callout function for service 0x36

Note: the callout function can, if needed, return also other NRCs but the ones above
won’t be treated by the Dcm module.

202 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.6.2.22 Service 0x37 - RequestTransferExit

This service is used to terminate a download or upload process.

[SWS_Dcm_00505] dThe Dcm module shall implement the RequestTransferExit (ser-
vice 0x37) of the Unified Diagnostic Services.c(RS_Diag_04033)
[SWS_Dcm_01134] dNRC described in Table 7.31 shall be the responsibility of the
callout function.c()
NRC Use Case
0x24 - requestSequenceError The programming process is not completed when a
request for this service is received.
0x72 - generalProgrammingFailure If the server detects an error when finalizing the
data transfer between the client and server (e.g.,
via an integrity check).

Table 7.31: NRC managed by callout function for service 0x37

Note: the callout function can, if needed, return also other NRC but the ones above
won’t be treated by the Dcm module.
[SWS_Dcm_00759] dIf the operation Xxx_ProcessRequestTransferExit returns
value E_NOT_OK, the Dcm module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.c()

7.6.2.23 Service 0x38 - RequestFileTransfer

[SWS_Dcm_01083] dThe Dcm module shall implement the RequestFileTransfer (ser-

vice 0x38) of the Unified Diagnostic Services.c()
This service is used to request the start of a file transfer process according to ISO-
14229-1.
[SWS_Dcm_01446] dIf the DcmRequestFileTransferUsePort is set to TRUE the
Dcm shall use C/S calls of the interface RequestFileTransfer for all RequestFileTransfer
related callouts.c()
[SWS_Dcm_01447] dIf the DcmRequestFileTransferUsePort is set to FALSE the
Dcm shall use C function calls for all RequestFileTransfer related callouts.c()
[SWS_Dcm_01448] dIf the fileSizeParameterLength parameter in the RequestFile-
Transfer request is present and outside the closed interval [0x01..0x08], the Dcm shall
send a negative response with NRC 0x31 (RequestOutOfRange).c()
[SWS_Dcm_01449] dIf the modeOfOperation parameter in the RequestFileTransfer
request is not supported (0x00 or greater than 0x05), the Dcm shall send a negative
response with NRC 0x31 (RequestOutOfRange).c()

203 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01450] dThe Dcm shall process RequestFileTransfer according to [5] and,

in case of modeOfOperation equal to 0x01 (AddFile) call XXX_ProcessRequestAddFile
after the full length check.c()
[SWS_Dcm_01451] dThe Dcm shall process RequestFileTransfer accord-
ing to [5] and, in case of modeOfOperation equal to 0x02 (DeleteFile) call
XXX_ProcessRequestDeleteFile after the full length check.c()
[SWS_Dcm_01452] dThe Dcm shall process RequestFileTransfer accord-
ing to [5] and, in case of modeOfOperation equal to 0x03 (ReplaceFile) call
XXX_ProcessRequestReplaceFile after the full length check.c()
[SWS_Dcm_01453] dThe Dcm shall process RequestFileTransfer accord-
ing to [5] and, in case of modeOfOperation equal to 0x04 (ReadFile) call
XXX_ProcessRequestReadFile after the full length check.c()
[SWS_Dcm_01454] dThe Dcm shall process RequestFileTransfer accord-
ing to [5] and, in case of modeOfOperation equal to 0x05 (ReadDir) call
XXX_ProcessRequestReadDir after the full length check.c()
[SWS_Dcm_01088] dIf any of the file transfer operations XXX_ProcessRequest<yyy>
returns value E_NOT_OK, the Dcm module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.c()
[SWS_Dcm_01455] dThe Dcm shall use the value configured in DcmRequestFile-
TransferFileSizeOrDirInfoParameterLength as value sent in fileSizeOrDirIn-
foParameterLength in the response.c()
[SWS_Dcm_01090] dThe Dcm shall use the value configured in DcmRequestFile-
TransferFileSizeOrDirInfoParameterLength as number of bytes sent in file-
SizeUncompressedOrDirInfoLength and fileSizeCompressed in the response.c()
[SWS_Dcm_01456] dThe Dcm shall use the value configured in DcmRequestFile-
TransferLengthFormatIdentifier as value sent in lengthFormatIdentifier in the
response.c()
[SWS_Dcm_01091] dThe Dcm shall use the value configured in DcmRequestFile-
TransferLengthFormatIdentifier as number of bytes sent in maxNumberOf-
BlockLength in the response.c()
[SWS_Dcm_01457] dIf the maxNumberOfBlockLength does not fit into the requested
lengthFormatIdentifier number of bytes, the Dcm shall send NRC 0x10 (generalReject).c
()
[SWS_Dcm_01458] dIf the fileSizeUncompressedOrDirInfoLength or fileSizeCom-
pressed do not fit into the requested fileSizeOrDirInfoParameterLength number of
bytes, the Dcm shall send NRC 0x10 (generalReject).c()

204 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.6.2.24 Service 0x85 - ControlDTCSetting

An external test tool can request an ECU to either disable or enable DTC storage in the
ECUs error memory by sending a UDS Service 0x85 request with sub-function 0x01
("ON") or 0x02 ("OFF").
[SWS_Dcm_00249] dThe Dcm module shall implement UDS Service ControlDTCSet-
ting (0x85) to enable or disable the storage of DTCs in the ECUs error memory.c(RS_-
Diag_04159)
[SWS_Dcm_01399] dIf the Dcm receives a ControlDTCSetting (0x85) service with
DTCSettingControlOptionRecord != 0xFFFFFF, the Dcm shall send a NRC 0x31 (Re-
questOutOfRange).c(RS_Diag_04159)
[SWS_Dcm_01063] dOn reception of UDS Service 0x85 with subfunction 0x01 (DTC-
SettingType "ON"), the Dcm shall call Dem_EnableDTCSetting() with ClientId = Client
Id for this Dcm instance (see DcmDemClientRef).c(RS_Diag_04115)
[SWS_Dcm_00783] dIn case of Dem_EnableDTCSetting returns
E_OK (see [SWS_Dcm_01063]), the Dcm shall invoke a mode
switch of the ModeDeclarationGroupPrototype DcmControlDTC-
Setting by calling SchM_Switch_<bsnp>_DcmControlDTCSetting
(RTE_MODE_DcmControlDTCSetting_ENABLEDTCSETTING).c()
[SWS_Dcm_00406] dOn reception of UDS Service 0x85 with subfunction 0x02 (DTC-
SettingType "OFF"), the Dcm shall call Dem_DisableDTCSetting() with ClientId = Client
Id for this Dcm instance (see DcmDemClientRef).c(RS_Diag_04115)
[SWS_Dcm_00784] dIn case of Dem_DisableDTCSetting returns
E_OK (see [SWS_Dcm_00406] ), the Dcm shall invoke a mode
switch of the ModeDeclarationGroupPrototype DcmControlDTC-
Setting by calling SchM_Switch_<bsnp>_DcmControlDTCSetting
(RTE_MODE_DcmControlDTCSetting_DISABLEDTCSETTING).c()
[SWS_Dcm_00751] dIn case the DTCSetting is disabled and a transitions to de-
fault session or upon any diagnostic session change where the new session does
not support UDS Service ControlDTCsetting anymore, the Dcm module shall call
Dem_EnableDTCSetting() with the following parameters
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
and switch the mode DcmControlDTCSetting to DCM_ENABLEDTCSETTING.c()
For some use-cases the Dcm may re-enable the controlDTCsetting due to external
changed mode conditions:
[SWS_Dcm_00752] dIn case the DTCSetting is disabled and at least one ref-
erenced arbitrary ModeDeclarationGroupPrototypes (see configuration parameter
DcmDspControlDTCSettingReEnableModeRuleRef) for service ControlDTCSet-
ting (0x85) with DTCSettingType "OFF" (0x02) are not fulfilled anymore, the Dcm mod-
ule shall call Dem_EnableDTCSetting() with the following parameters:

205 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)

and switch the mode DcmControlDTCSetting to DCM_ENABLEDTCSETTINGc()
Note: If at least one ModeDeclarationGroupPrototypes is configured (see configuration
parameter DcmDspControlDTCSettingReEnableModeRuleRef) for service Con-
trolDTCSetting (0x85) with DTCSettingType "OFF" (0x02), it is recommended to acti-
vate the condition check for the according sub-function 0x02(see configuration param-
eter DcmDsdSubServiceModeRuleRef).
Note: This active observation of the referenced mode declaration groups can either be
achieved by polling the mode condition in each MainFunction cycle or by attaching to
the change notification of mode declaration group (SchM will trigger a BSWEntitiy in
Dcm on changes of this mode declaration group).
[SWS_Dcm_00829] dIf the configuration parameter DcmSupportDTCSettingCon-
trolOptionRecord is set to true and the length of DTCSettingControlOptionRecord
in the request is different from 3 bytes, the Dcm shall return NRC 0x13 (Incorrect mes-
sage length or invalid format).c()
[SWS_Dcm_00852] dIf the configuration parameter DcmSupportDTCSettingCon-
trolOptionRecord is set to false and the request contains any data after the sub-
function, the Dcm shall return NRC 0x13 (Incorrect message length or invalid format).c
()
[SWS_Dcm_01564] dIf the configuration parameter DcmSupportDTCSettingCon-
trolOptionRecord is set to false and the request contains any data after the sub-
function, the Dcm shall return NRC 0x13 (Incorrect message length or invalid format).c
()

7.6.2.25 Service 0x87 - LinkControl

This service is used to gain bus bandwidth for diagnostic purposes.

The Service LinkControl (0x87) is user optional. There are different project specific
use cases which are not handled in the default Dcm. One use case is to switch the
bandwidth in application an other use case performs an OEM bootloader jump.
Therefore the service LinkControl needs to be implemented project specific as external
service (refer to Chapter 8.8 Dcm as Service-Component).

7.6.3 OBD Services

7.6.3.1 Overview

The following table defines the OBD Services supported by the DCM.

206 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Relevant OBD Ser- Support in the DCM

vice Identifier
$01 Supported
$02 Supported
$03 Supported
$04 Supported
$06 Supported
$07 Supported
$08 Supported
$09 Supported
$0A Supported

Table 7.32: Support for OBD services in the DCM

7.6.3.2 General behavior

In many cases, the Dcm protocol allows the bundling of several requests (for example
several "PIDs") and the corresponding bundling of the responses. The descriptions of
the behavior for the individual services do not explicitly consider this. As the Dcm needs
to comply with OBD standard (as is defined through various requirements below), the
Dcm might need to repeat the steps defined below to parse a request and assemble a
valid response.
In a vehicle there can be 3 different types of OBD ECUs:
• Master ECU (one per vehicle)
• Primary ECU (several per vehicle)
• Dependent / Secondary ECUs (several per vehicle)
From the Basic Software point of view Dependent / Secondary ECUs doesn’t need any
specific OBD functionality. In Dependent / Secondary ECUs OBD-relevant information
will not be stored in the Basic Software (e.g. no direct communication with the scan
tool). The respective OBD functionality might be handled in Dependent / Secondary
ECUs by a SWC.
The following OBD requirements are only valid for Master and Primary ECUs. If neces-
sary the OBD requirements differentiate between Master and Primary Requirement.
The following table gives an overview about which OBD functionality must be supported
in a Master ECU, Primary ECU or Dependent / Secondary ECU:
Functionality Master ECU Primary ECU Dependent /
Secondary ECU
OBD Scantool Yes Yes No
Communication

Table 7.33: Overview about OBD functionality in different OBD ECUs

207 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00077] dWhen calling the DEM module for OBD services, the Dcm module
shall use the following values for the parameter DTCOrigin:
Service $0A uses DEM_DTC_ORIGIN_PERMANENT_MEMORY
All other services use DEM_DTC_ORIGIN_OBD_RELEVANT_MEMORYc(RS_Diag_-
04058)

7.6.3.3 Service $01 - Request Current Powertrain Diagnostic Data

[SWS_Dcm_00243] dThe Dcm module shall implement the OBD service $01 (Request
Current Powertrain diagnostic Data) in compliance to all provisions of the OBD stan-
dard.c()
Using Service $01, an external test tool can request an emission-related ECU to return
PID-values or to return the supported PIDs. OBD reserves certain PIDs for the special
purpose of obtaining the list of available PIDs in a certain range. These PIDs are called
"availability PIDs" and are $00, $20, $40, $60, $80, $A0, $C0 an $E0.
The Dcm collects the PID information from 1 to n SW-Cs. This applies in particular
for PIDs which contain several data values for potentially different sources. Example:
PID$83 reports Nox Sensor Data for sensor 1 and sensor 2 in one composed PID
which might come from different SW-C.
The Dcm configuration defines the PIDs that are available on the ECU. The Dcm con-
figuration defines for each such PID:
• The PID Identifier (see configuration parameter DcmDspPidIdentifier)
• Indication of the PID is used or not (for postbuild configuration) (see configuration
parameter DcmDspPidUsed)
• The size of the PID (see configuration parameter DcmDspPidSize)
• The supported information for this PID (see configuration parameter DcmDsp-
PidSupportInfo)
• List of data (DcmDspPidData) for the PID with the following configuration for
every data
– The length of the data associated with the PID (see configuration parameter
DcmDspPidDataByteSize)
– The position of the data in the PID (see configuration parameter DcmDsp-
PidByteOffset)
– The reference to the supported information container (see configuration pa-
rameter DcmDspPidDataSupportInfo)
– The Xxx_ReadData() function that the Dcm must call to obtain the current
value of the data or the name of the port that the Dcm uses to obtain the

208 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

current value through the RTE from a SW-C (see configuration parameters
DcmDspPidDataReadFnc and DcmDspPidDataUsePort)
[SWS_Dcm_00407] dOn reception of an OBD Service $01 request with only "avail-
ability PIDs" as parameter, the Dcm shall respond with the corresponding supported
(=configured) PIDs encoded according to the OBD standard.c()
To obtain the value for a PID, the Dcm uses the configured Xxx_ReadData() functions
for every data of the PID. To provide OBD Service $01, the Dcm relies on external
functions that allow it to obtain the value of the PIDs. There is one such function per
data of every PID that is needed by the DCM.
When using a Xxx_ReadData() function, the Dcm provides a buffer of the correct length,
which is filled by the function with the data PID value.
[SWS_Dcm_00408] dOn reception of an OBD Service $01 request with only PIDs that
are not "availability PIDs", the Dcm shall obtain the current value of these PIDs by
invoking the configured Xxx_ReadData() functions for every data of the PID and shall
return these values as response to Service $01.c()
[SWS_Dcm_00943] dOn reception of an OBD Service $01 request with a mixure of
"avalibility PIDs" and not "avalibility PIDs", this request shall be ignored by the Dcm.c()
The entity providing the actual implementation of the Xxx_ReadData() function for a
specific signal of a PID might be a SW-C or another basic software module. The origin
of the function is not known to the Dcm but is part of the Dcm configuration. Some
PIDs are provided by the DEM. These PIDs are also explicitly configured in the Dcm
configuration and it is the responsibility of a correct Dcm configuration to make the
Xxx_ReadData() function point to the correct function provided by the DEM.
[SWS_Dcm_CONSTR_6069] Dependency for DcmDspPidDataReadFnc dDcmD-
spPidDataReadFnc shall be only present if DcmDspPidDataUsePort is set to
USE_DATA_SYNCH_FNC.c()
For certain PIDs, the Dem provides the function to obtain the PID value. Which PIDs
come from the Dem are part of the Dcm configuration.
Note: For PIDs where Dem provides the function, DcmDspPidDataUsePort for that
PID should be set to USE_DATA_SYNCH_FNC and DcmDspPidDataReadFnc shall
point to the function Dem_DcmReadDataOfPID<NN> where <NN> represents the Id
of the PID.
The data byte A of the PIDs contain the support status of the subsequent data bytes.
Since not all data values might be available due to the particular vehicle configuration
(e.g. there is only a Nox-sensor 1 available in the vehicle in the example above), the
PID response contains in this data byte A the information about the support status of
the following data values. Note, that the PIDs always contain the same number of bytes
- even if not all values are really available.

209 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00621] dIf a PID contains support information (presence of DcmDspPid-

DataSupportInfo container) the Dcm shall add the support information in the diag-
nostic response.c()
[SWS_Dcm_00622] dIf a PID contains support information (presence of DcmDspPid-
DataSupportInfo container) the Dcm shall calculate the support information value
according to the available data for this PID: for every DcmDspPidData container ex-
isting for this PID, the associated support information bits, referenced in DcmDspPid-
DataSupportInfo, shall be set to onec()
The response to the OBD-tester needs to be composed out of the available data values.
Data bytes that are not provided by an SW-C need to be replaced with fill-byte to obtain
a complete PID contents.
[SWS_Dcm_00623] dWhen responding to OBD Service $01, the Dcm shall put fill-bytes
between DcmDspPidData in the PID whenever content bytes are missing in order to
fit to the PID size (see configuration parameter DcmDspPidSize).c()
[SWS_Dcm_00944] dThe Dcm shall set the fill bytes to 0x00.c()
Note: If other fill-bytes than 0x00 are needed by legistlation, the application has to
provide the value of the fill-byte.
[SWS_Dcm_00718] dTo serialize the required AUTOSAR data types (signed- and
unsigned integer) into the response message of OBD Service $01 responses
the target endianness configured in DcmDspPidDataEndianness shall be con-
sidered for DcmDspPidData elements having DcmDspPidDataUsePort set to
USE_DATA_SENDER_RECEIVER or USE_DATA_SENDER_RECEIVER_AS_SERVICE.
In case DcmDspPidDataEndianness is not present, the DcmDspDataDefault-
Endianness shall be used instead.c()
[SWS_Dcm_CONSTR_6068] Dependency for DcmDspPidDataEndianness dIn
case DcmDspPidDataEndianness is not present, the DcmDspDataDefaultEndi-
anness shall be used instead.c()

7.6.3.4 Service $02 - Request Power Train FreezeFrame Data

[SWS_Dcm_00244] dThe Dcm shall implement OBD Service $02 (Request Power Train
FreezeFrame Data) in compliance to all provisions of the OBD standard.c()
For OBD-relevant FreezeFrames AUTOSAR only supports frame 0, which is the mini-
mum required by legislation.
[SWS_Dcm_00409] dThe Dcm shall ignore all requests regarding record-numbers that
are not 0c()
[SWS_Dcm_00972] dOn reception of an OBD Service $02 request with a mixure of
"availability PIDs" and not "availability PIDs", this request shall be ignored by the
Dcm.c()

210 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00973] dWhen responding to OBD Service $02, the Dcm shall put fill-bytes
between DcmDspPidData in the PID whenever content bytes are missing in order to
fit to the PID size (see configuration parameter DcmDspPidSize).c()
[SWS_Dcm_00974] dThe Dcm shall set the fill bytes to 0x00.c()
Note: If other fill-bytes than 0x00 are needed by legislation, the application has to
provide the value of the fill-byte.
The following sections define how specific PIDs are handled by the Dcm.

7.6.3.4.1 Service $02 - PID$02

An external tester can request the DTC that caused a FreezeFrame to be stored by
using the Service $02 with the PID value $02.
[SWS_Dcm_00279] dOn reception of a request for Service $02 with PID $02, the Dcm
shall call Dem_DcmGetDTCOfOBDFreezeFrame() with FrameNumber set to 0x00 to
get the DTC number.c(RS_Diag_04058)
The Dem module returns the corresponding DTC. Note that this 2-byte DTC is packed
into the 4-byte data returned by the call to Dem_DcmGetDTCOfOBDFreezeFrame ().
see Dem specification on how this is done.
[SWS_Dcm_01061] dIf Dem_DcmGetDTCOfOBDFreezeFrame returns E_NOT_OK,
the Dcm shall answer positively with $0000 (indicates no stored freeze frame data).c()

7.6.3.4.2 Service $02 - availability PID

Using Service $02, an external tester may request the supported PIDs for a specific
freeze-frame by using the "availability PIDs".
[SWS_Dcm_00284] dOn reception of a service $02 request with an "availability PID",
the Dcm shall respond with the corresponding supported (=configured) PIDs encoded
according to the OBD standard.c()

7.6.3.4.3 Service $02 - other PIDs

Using Service $02, an external tester may request the values of specific PIDs in specific
FreezeFrames.
[SWS_Dcm_00286] dOn reception of a service $02 request with a
PID that is not an "availability PID" and is not $02, the Dcm shall call
Dem_DcmReadDataOfOBDFreezeFrame() for every data of the PID with the
following parameter values:
• PID = the PID received in the OBD request

211 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• DestBuffer = a buffer in which the callee can write the value of the PID
• BufSize = the size of the DestBuffer, this must be at least equal to the size needed
to store the value of the PID as configured in the DCM
• DataElementIndexOfPid = implicit index (from 0 to n) of the DataElement calcu-
lated by Dcm according to the order of the DataElement positions in the PID (see
parameter DcmDspPidByteOffset)
c()
Note that is not necessary for the Dcm module to lock or unlock the record updates of
the Dem module.
[SWS_Dcm_00287] dUpon the completion of [SWS_Dcm_00286], the Dcm shall gen-
erate a response message including the respective PID, FreezeFrame Number and
the associated data record for the requested FreezeFrame number.c()
[SWS_Dcm_01252] dIf Dem_DcmReadDataOfOBDFreezeFrame() returns
E_NOT_OK and a single PID is requested, the Dcm shall not provide any answer.c()
[SWS_Dcm_01253] dIf Dem_DcmReadDataOfOBDFreezeFrame() returns
E_NOT_OK and all PIDs from the requested multiple PID(s) are not supported,
the Dcm shall not provide any answer.c()
[SWS_Dcm_01254] dIf Dem_DcmReadDataOfOBDFreezeFrame() returns
E_NOT_OK and at least one PID from the requested multiple PID(s) is sup-
ported, the Dcm shall send a positive response including the data of the supported
PID(s).c()

7.6.3.5 Service $03 $07 $0A - Obtaining DTCs

[SWS_Dcm_00245] dThe Dcm module shall implement OBD Service $03 (Request
emission-related diagnostic trouble codes) in compliance to all provisions of the OBD
standard.c()
[SWS_Dcm_00410] dThe Dcm module shall implement OBD Service $07 (Request
Emission-Related Diagnostic Trouble Codes Detected during Current or Last Com-
pleted Driving Cycle) in compliance to all provisions of the OBD standard.c()
[SWS_Dcm_00411] dThe Dcm module shall implement OBD Service $0A (Request
Emission-Related Diagnostic Trouble Codes with Permanent Status) in compliance to
all provisions of the OBD standard.c()
An external test tool can request an emission-related ECU to report all stored, pending
or permanent emission-related DTCs by sending the request $03, $07, $0A respec-
tively.

212 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00289] dWhen receiving a request for OBD Service $03, the Dcm module
shall obtain from the DEM all DTCs in primary memory and with a "confirmed" status
using the functions Dem_SetDTCFilter() and Dem_GetNextFilteredDTC().c()
Note: The Dcm module can get an indication of the number of records that will be
found using Dem_GetNextFilteredDTC() by using Dem_GetNumberOfFilteredDTC().
This allows the implementation to calculate the total size of the response before cycling
through the DTCs.
[SWS_Dcm_00412] dWhen receiving a request for OBD Service $07, the Dcm module
shall obtain from the DEM module all DTCs in primary memory with a "pending" status
using the functions Dem_SetDTCFilter() and Dem_GetNextFilteredDTC().c()
Note: The Dcm module can get an indication of the number of records that will be
found using Dem_GetNextFilteredDTC() by using Dem_GetNumberOfFilteredDTC().
This allows the implementation to calculate the total size of the response before cycling
through the DTCs.
[SWS_Dcm_00330] dWhen receiving a request for OBD Service $0A, the Dcm module
shall obtain from the DEM all DTCs stored in permanent memory using the functions
Dem_SetDTCFilter() and Dem_GetNextFilteredDTC().c()
Note: The Dcm module can get an indication of the number of records that will be
found using Dem_GetNextFilteredDTC() by using Dem_GetNumberOfFilteredDTC().
This allows the implementation to calculate the total size of the response before cycling
through the DTCs.
The following table illustrates the parameters the Dcm module must use when calling
Dem_SetDTCFilter() in response to a request for OBD Service $03, $07 or $0A.
Parameters to Dem_SetDTCFilter
OBD Service $03 $07 $0A
ClientId Client Id for this Dcm Client Id for this Dcm Client Id for this Dcm
instance (see instance (see instance (see
DcmDemClientRef) DcmDemClientRef) DcmDemClientRef)
DTCStatusMask 0x08 (confirmed bit 0x04(pending bit set) 0x00
set)
DTCFormat DEM_DTC_ DEM_DTC_ DEM_DTC_
FORMAT_OBD FORMAT_OBD FORMAT_OBD
DTCOrigin DEM_DTC_ORIGIN_ DEM_DTC_ORIGIN_ DEM_DTC_ORIGIN_
OBD_RELEVANT_ OBD_RELEVANT_ PERMANENT
MEMORY MEMORY
FilterWithSeverity DEM_FILTER_WITH_ DEM_FILTER_WITH_ DEM_FILTER_WITH_
SEVERITY_NO SEVERITY_NO SEVERITY_NO
DTCSeverityMask Not relevant Not relevant Not relevant
FilterForFaultDetec- DEM_FILTER_FOR_ DEM_FILTER_FOR_ DEM_FILTER_FOR_
tionCounter FDC_NO FDC_NO FDC_NO

Table 7.34: Dem_SetDTCFilter Parameters

When using paged buffer mechanism, in some case, it’s possible that the number of
DTC matching the filter change between the calculation of the total size, needed for

213 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

the first page transmission, and the sending of the further pages. For this reason, the
requirement [SWS_Dcm_00587] and [SWS_Dcm_00588] shall be considered for the
implementation of this service.
[SWS_Dcm_01227] dDem_GetNextFilteredDTC returns DEM_NO_SUCH_ELEMENT
and at least one matching element could be retrieved before, the Dcm shall send a
positive response including these data elements and the number of DTCs.c()
[SWS_Dcm_01228] dIf Dem_GetNextFilteredDTC returns
DEM_NO_SUCH_ELEMENT and no matching element could be retrieved be-
fore, the Dcm shall send a positive response with the number of DTCs set to 0x00.c
()

7.6.3.6 Service $04 - Clear/reset emission-related diagnostic information

[SWS_Dcm_00246] dThe Dcm module shall implement OBD Service $04 (Clear/re-
set emission-related diagnostic information) in compliance to all provisions of the OBD
standard.c()
An external test tool can request an emission-related ECU to clear the error memory
by sending the request $04.
[SWS_Dcm_00004] dWhen receiving a request for OBD Service $04, the Dcm module
shall call the interface Dem_SelectDTC with the following parameter values:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
• DTC = DEM_DTC_GROUP_ALL_DTCS
• DTCFormat = DEM_DTC_FORMAT_OBD
• DTCOrigin = DEM_DTC_ORIGIN_OBD_RELEVANT_MEMORY
c(RS_Diag_04058)
[SWS_Dcm_00413] dIn case Dem_ClearDTC() returns E_OK, the Dcm module shall
send a positive response.c()
[SWS_Dcm_00703] dIn case Dem_ClearDTC() returns DEM_PENDING, the Dcm shall
invoke Dem_ClearDTC() on next Dcm_MainFunction call again. It is up to the Dcm
to send NRC 78 (ResponsePending) to respect the response behaviourc(RS_Diag_-
04249)
[SWS_Dcm_00704] dIn case Dem_ClearDTC() returns DEM_CLEAR_FAILED, the
Dcm shall send a negative response 0x22 (conditionsNotCorrect).c()
[SWS_Dcm_00967] dIn case Dem_ClearDTC() returns DEM_CLEAR_BUSY, the Dcm
shall send a negative response 0x22 (ConditionsNotCorrect).c()

214 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_01067] dIn case Dem_ClearDTC() returns

DEM_CLEAR_MEMORY_ERROR, the Dcm module shall send a negative response
0x22 (ConditionNotCorrect).c()

7.6.3.7 Service $06 - Request On-Board Monitoring Test-results for Specific

Monitored Systems

7.6.3.7.1 General requirements

[SWS_Dcm_00414] dThe Dcm module shall implement OBD Service $06 (Request On-
Board Monitoring Test-results for Specific Monitored Systems) in compliance to all pro-
visions of the OBD standard.c()
Using Service $06, an external test tool can request an emission-related ECU to return
the DTR’s associated with the OBDMID or to return the supported OBDMIDs. OBD
reserves certain OBDMIDs for the special purpose of obtaining the list of supported
OBDMIDs in a certain range. These OBDMIDs are called "availability OBDMIDs" and
are $00, $20, $40, $60, $80, $A0, $C0 an $E0.
A tester request for supported OBDMIDs may contain up to six (6) "availability OBD-
MIDs".
[SWS_Dcm_00945] dOn reception of an OBD Service $06 request with "availability
OBDMIDs" together with other OBDMIDs as parameter, the Dcm module shall ignore
the request.c()
[SWS_Dcm_00956] dOn reception of an OBD Service $06 request with multiple non-
availability OBDMIDs, the Dcm module shall ignore the request.c()

7.6.3.7.2 Test results obtained via Dem interaction

The maintenance of the DTRs lies within the responsibility of the DEM. SW-Cs report-
ing DTRs use dedicated interfaces offered by the DEM. Upon requests from the tester
the Dcm retrieves the information from the DEM using dedicated DEM interfaces. There
is no direct interaction between the Dcm and SW-Cs.
[SWS_Dcm_00957] dOn reception of an OBD Service $06 request with only "availability
OBDMID(s)" as parameter(s), the Dcm module shall obtain the supported OBDMIDs by
calling the Dem interface Dem_DcmGetAvailableOBDMIDs()for each "availability OBD-
MID ($00, $20, ...)" contained within the request and concatenate the results within the
response message according to ISO-15031-5 [2].c()
[SWS_Dcm_00958] dOn reception of an OBD Service $06 request with an OBDMID
that is not an "availability OBDMID", the Dcm module shall call the DEM interface
Dem_DcmGetNumTIDsOfOBDMID() to obtain the TIDs available for the requested OB-
DMID and then recurrently call the interface Dem_DcmGetDTRData() for the number
of reported TIDs to obtain the associated DTR data.c()

215 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.6.3.8 Service $08 - Request Control of On-Board System, Test or Component

[SWS_Dcm_00417] dThe Dcm module shall implement OBD Service $08 (Request
Control of On-Board System, Test or Component) in compliance to all provisions of
the OBD standard.c()
Using Service $08, an external test tool can control an on-board system, test or com-
ponent using a TID. OBD reserves certain TIDs for the special purpose of obtaining the
list of supported TIDs in a certain range. These TIDs are called "availability TIDs" and
are $00, $20, $40, $60, $80, $A0, $C0 an $E0.
The Dcm module’s configuration defines the TIDs that are available on the ECU for
the purpose of OBD Service $08. The configuration defines for each such TID (see
configuration parameter DcmDspRequestControlTestId):
• the name of the port the Dcm uses to access the RequestControlServices inter-
face (see configuration parameter DcmDspRequestControl)
• the number of bytes this function takes as input (see configuration parameter
DcmDspRequestControlInBufferSize)
• the number of bytes this function writes as output (see configuration parameter
DcmDspRequestControlOutBufferSize)
To provide OBD Service $08, the Dcm relies on external functions configured per TID.
[SWS_Dcm_00418] dOn reception of an OBD Service $08 request with one or more
"availability TIDs" as parameter, the Dcm module shall respond with the corresponding
supported (=configured) TIDs.c()
[SWS_Dcm_00947] dOn reception of an OBD Service $08 request "availability TIDs"
together with other TIDs as parameter, the Dcm module shall ignore the request.c()
[SWS_Dcm_00419] dOn reception of an OBD Service $08 request with a TID that is not
an "availability TID", the Dcm module shall invoke the configured Xxx_RequestControl()
function with the following parameters values: InBuffer: data contained in the OBD
request (the size of which must correspond to the size configured in the Dcm module’s
configuration) OutBuffer: space in which the RequestControl function can store its
result (the size of the buffer is taken from the Dcm module’s configuration)c()
[SWS_Dcm_00420] dAfter the execution of [SWS_Dcm_00419], the Dcm module shall
respond to the service request using the data stored by the RequestControl function in
the OutBuffer.c()
[SWS_Dcm_00948] dAs specified in [3, SAE J1979], unused data bytes shall be filled
with $00.c()
[SWS_Dcm_01192] dIf Xxx_RequestControl() doesn’t return E_OK, the Dcm shall re-
turn NRC 0x22.c()

216 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

7.6.3.9 Service $09 - Request Vehicle Information

[SWS_Dcm_00421] dThe Dcm module shall implement OBD Service $09 (Request Ve-
hicle Information) in compliance to all provisions of the OBD standard.c()
Using Service $09, an external test tool can request vehicle information or can obtain
lists of supported vehicle information. OBD reserves certain InfoTypes for the special
purpose of obtaining the list of supported InfoTypes in a certain range. These Infotypes
are called "availability InfoTypes" and are $00, $20, $40, $60, $80, $A0, $C0 an $E0.
The Dcm module’s configuration defines the InfoTypes and associated data that are
available on one or several SW-C. The configuration defines for each such InfoType:
• The value of InfoType (see configuration parameter DcmDspVehInfoInfoType)
• For every data of the InfoType:
– The position of this data in the InfoType (see configuration parameter DcmD-
spVehInfoDataOrder)
– the size of the value of the InfoType data (see configuration parameter
DcmDspVehInfoDataSize)
– the function that the Dcm module must call to obtain the value for this Info-
Type data OR the port-name through which the Dcm module can obtain the
value for this InfoType data (see configuration parameter DcmDspVehInfo-
DataReadFnc and DcmDspVehInfoDataUsePort).
To provide OBD Service $09, the Dcm relies on external functions that allow it to obtain
the value of an InfoType data. There is one such function per InfoType data that is
needed by the DCM.
When invoking a Xxx_GetInfotypeValueData() function, the Dcm module provides a
buffer of the correct size in which the value of the InfoType data can be stored. The
entity providing the actual implementation of the Xxx_GetInfotypeValueData() function
for a specific InfoType data might be a SW-C or another basic software module. The
origin of the function is part of the Dcm module’s configuration.
Certain InfoTypes needed by the Dcm to provide Service $09 are provided by the DEM.
This is handled in the Dcm configuration.
[SWS_Dcm_00422] dOn reception of an OBD Service $09 request with one or more
"availability InfoTypes" as parameter, the Dcm module shall respond with the corre-
sponding supported (=configured) InfoTypes.c()
[SWS_Dcm_00949] dOn reception of an OBD Service $09 request "availability Info-
Types" together with other InfoTypes as parameter, the Dcm module shall ignore the
request.c()
[SWS_Dcm_00423] dOn reception of an OBD Service $09 request for an InfoType that
is not an "availability InfoType", the Dcm module shall obtain the value of this InfoType

217 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

by invoking all the configured Xxx_GetInfotypeValueData() function for every data of

this InfoType and shall return the value as response to Service $09c()
[SWS_Dcm_00684] dIn case DcmDspVehInfoNODIProvResp is set to FALSE, in
addition to collect the available InfoType value contributions from the individual SW-C,
the Dcm shall compute the data byte NofDataItems in the diagnostic response, which
defines the number of DataItems included in one InfoType.c()
Note: The Calculation of the Calibration Identification (CAL-ID) and Calibration Verifi-
cation Number (CVN) is not a BSW Task and will not handled within the DCM.
[SWS_Dcm_01167] dIn case DcmDspVehInfoNODIProvResp is set to TRUE, the
Dcm shall take over the value returned by the provider and report it as NofDataItems in
the diagnostic response.c()
[SWS_Dcm_CONSTR_6045] dIn case the responsibility is on provider side (DcmD-
spVehInfoNODIProvResp is set to TRUE), only one DcmDspVehInfoData con-
tainer shall be allowed.c()
[SWS_Dcm_CONSTR_6046] dIn case DcmDspVehInfoDataUsePort
is set to FALSE and DcmDspVehInfoDataReadFnc is set to either
Dem_DcmGetInfoTypeValue08 or Dem_DcmGetInfoTypeValue0B then DcmD-
spVehInfoNODIProvResp shall be set to TRUE.c()
Note : The integrator has to make sure that the buffer determined by the DcmDspVe-
hInfoDataSize is sufficiently sized to receive the data returned by the provider of
the data.
[SWS_Dcm_01191] dIf Xxx_GetInfoTypeValueData() doesn’t return E_OK or
E_PENDING, the Dcm shall return NRC 0x12.c()

7.6.4 Interaction usecases

The Dcm shall be able to manage a jump to the bootloader / jump due to ECUReset
request. Due to the diversity of possibility to realize this jump, this will be done using
callout call.

7.6.4.1 Jump to Bootloader

4 different use cases have been identified for the jump to the bootloader, if all precon-
ditions are fulfilled and assuming the ’suppressPosRspMsgIndicationBit ’ flag is set to
’false’:
1. The application immediately sends a final positive response and then jumps to
the bootloader
2. The application first sends a NRC 0x78 response, then the final positive response
and afterwards jumps to the bootloader

218 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

3. The application immediately jumps to the bootloader and the bootloader sends
the final positive response
4. The application first sends a NRC 0x78 response, then jumps to the bootloader
and the bootloader sends the final positive response
Note: In case the ’suppressPosRspMsgIndicationBit’ flag is set to ’true’, use case ’1’
and use case ’3’ will not issue a positive response.
[SWS_Dcm_00532] dOn reception of service DiagnosticSessionControl if the provided
session is used to jump to OEM bootloader (parameter DcmDspSessionForBoot
set to DCM_OEM_BOOT or DCM_OEM_BOOT_RESPAPP) the Dcm shall prepare the
jump to the OEM bootloader (see [SWS_Dcm_00535]) by triggering the mode switch
of ModeDeclarationGroupPrototype DcmEcuReset to JUMPTOBOOTLOADER.c(RS_-
Diag_04098)
Note: By this mode switch the Dcm informs the BswM to prepare the jump to the boot-
loader.
[SWS_Dcm_00592] dOn reception of service DiagnosticSessionControl if the provided
session is used to jump to System Supplier bootloader (parameter DcmDspSession-
ForBoot set to DCM_SYS_BOOT or DCM_SYS_BOOT_RESPAPP) the Dcm shall
prepare the jump to the System Supplier bootloader (see [SWS_Dcm_00535]) by trig-
gering the mode switch of ModeDeclarationGroupPrototype DcmEcuReset to JUMP-
TOSYSSUPPLIERBOOTLOADERc(RS_Diag_04098)
Note: By this mode switch the Dcm informs the BswM to prepare the jump to the boot-
loader.
[SWS_Dcm_01164] dIn case the service DiagnosticSessionControl implies an ECU
reset, the Dcm shall ignore all further requests while that reset is being processed.c()
[SWS_Dcm_00654] dIn case the ModeDeclarationGroupPrototype DcmEcuReset
is switched to mode JUMPTOBOOTLOADER or JUMPTOSYSSUPPLIERBOOT-
LOADER and the configuration parameter DcmSendRespPendOnRestart is set to
TRUE, the Dcm shall trigger transmission of NRC 0x78 - RCR-RP.c(RS_Diag_04098,
RS_Diag_04249)
Note: This final transmission of NRC 0x78 before switching to Bootloader shall reload
the P2* timeout in the client.
[SWS_Dcm_01175] dIn case the ModeDeclarationGroupPrototype DcmEcuReset can
not be switched JUMPTOBOOTLOADER or JUMPTOSYSSUPPLIERBOOTLOADER,
the Dcm shall answer negatively to the request with NRC 0x22 (Conditions not correct).c
()
[SWS_Dcm_00535] dIf the jump to bootloader is requested (see [SWS_Dcm_00532],
[SWS_Dcm_00592], the configuration parameter DcmSendRespPendOnRestart is
set to TRUE (see [SWS_Dcm_00654]) and the configuration parameter DcmDspSes-
sionForBoot is set to DCM_OEM_BOOT or DCM_SYS_BOOT, the Dcm shall call

219 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Dcm_SetProgConditions after a successful transmission of NRC 0x78 (Response

pending).c(RS_Diag_04098)
This will allow to store all relevant information prior to jumping to the bootloader.
Note: It is up to the software integrator to decide where to store that data. Usually it
will be stored in non-volatile memory like e.g. data flash. It is also acceptable to "store"
this data in a RAM section which is not initialized out of reset.
[SWS_Dcm_01163] dIn the context of a request to jump to the bootloader (see
[SWS_Dcm_00532] and [SWS_Dcm_00592]), after Dcm_SetProgConditions re-
turns E_OK according to [SWS_Dcm_00535], the Dcm shall trigger the mode switch of
the ModeDeclarationGroupPrototype DcmEcuReset to EXECUTE.c(RS_Diag_04098)
[SWS_Dcm_01177] dIf the jump to bootloader is requested (see [SWS_Dcm_00532],
[SWS_Dcm_00592], the configuration parameter DcmSendRespPendOn-
Restart is set to TRUE (see [SWS_Dcm_00654]), and the configuration pa-
rameter DcmDspSessionForBoot is set to DCM_OEM_BOOT_RESPAPP or
DCM_SYS_BOOT_RESPAPP, the Dcm shall initiate the final response after a
successful transmission of NRC 0x78 (Response pending).c(RS_Diag_04098)
[SWS_Dcm_00995] dIf the NRC 0x78 (Response Pending) response in
[SWS_Dcm_00535] is not sent successfully the Dcm shall cancel the current
request.c()
[SWS_Dcm_00997] dIf the NRC 0x78 (Response Pending) response in
[SWS_Dcm_00535] is not sent successfully no jump to the bootloader shall be
performedc()
Note: If the NRC 0x78 (Response Pending) response has not been sent correctly the
Dcm will stay in the application and wait for the next request from the Client.
[SWS_Dcm_01178] dIn case the ModeDeclarationGroupPrototype DcmEcuReset
is switched to mode JUMPTOBOOTLOADER or JUMPTOSYSSUPPLIERBOOT-
LOADER, the configuration parameter DcmSendRespPendOnRestart is set to
FALSE and the configuration parameter DcmDspSessionForBoot is set to
DCM_OEM_BOOT_RESPAPP or DCM_SYS_BOOT_RESPAPP , the Dcm shall initi-
ate the final responsec()
[SWS_Dcm_01179] dIn case the final response has been successfully sent according
to [SWS_Dcm_01177] or [SWS_Dcm_01178], the Dcm shall call Dcm_SetProgCon-
ditionsc()
[SWS_Dcm_01180] dIf Dcm_SetProgConditions returns E_OK according to
[SWS_Dcm_01179], the Dcm shall trigger the mode switch of the ModeDeclara-
tionGroupPrototype DcmEcuReset to EXECUTE.c()
[SWS_Dcm_01181] dIf Dcm_SetProgConditions returns E_NOT_OK according to
[SWS_Dcm_01179], the Dcm shall not request any reset, shall not perform the jump to

220 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

bootloader, and shall not switch the ModeDeclarationGroupPrototype DcmEcuReset to

EXECUTE.c()
[SWS_Dcm_00720] dIn case the ModeDeclarationGroupPrototype DcmEcuReset
is switched to mode JUMPTOBOOTLOADER or JUMPTOSYSSUPPLIERBOOT-
LOADER, the configuration parameter DcmSendRespPendOnRestart is set to
FALSE and the configuration parameter DcmDspSessionForBoot it set to
DCM_OEM_BOOT or DCM_SYS_BOOT, the Dcm shall call Dcm_SetProgCondi-
tions immediately. (see [SWS_Dcm_00532] and [SWS_Dcm_00592])c()
[SWS_Dcm_00719] dIf Dcm_SetProgConditions returns E_OK according to
[SWS_Dcm_00720], the Dcm shall shall trigger the mode switch of the ModeDecla-
rationGroupPrototype DcmEcuReset to EXECUTE without sending a NRC 0x78 (Re-
sponse pending).c()
In case of [SWS_Dcm_00719], the exact response handling depends on the state of
the ’suppressPosRspMsgIndicationBit’ (TRUE or FALSE) in the request message.
[SWS_Dcm_00715] dIf the jump to bootloader is requested (see [SWS_Dcm_00532]
and [SWS_Dcm_00592]) and if the call to Dcm_SetProgConditions returns
E_NOT_OK (see [SWS_Dcm_00535] and [SWS_Dcm_00720]), no further action shall
be taken by the Dcm and negative response NRC 0x22 (Conditions not correct) shall be
returned.c()

7.6.4.2 Jump due to ECUReset

On reception of an ECUReset Service 0x11 request, if the configuration parameter

DcmResponseToEcuReset is set to AFTER_RESET, the Dcm will set the Respon-
seRequired flag by calling Dcm_SetProgConditions.
[SWS_Dcm_01423] Answer to ECUReset request dOn reception of an ECUReset
Service 0x11 request, if DcmResponseToEcuReset is set to AFTER_RESET, the Dcm
shall answer to EcuReset service after the reset.c(RS_Diag_04098)
[SWS_Dcm_01424] Answer to ECUReset request dOn reception of an ECUReset
Service 0x11 request, if DcmResponseToEcuReset is set to BEFORE_RESET, the
Dcm shall answer to EcuReset service before the reset.c(RS_Diag_04098)
[SWS_Dcm_01425] Answer to ECUReset request dIf the Dcm intiates a reset and
DcmSendRespPendOnRestart is set to TRUE, the Dcm shall trigger transmission of
NRC 0x78 (Response pending) before the reset.c(RS_Diag_04098, RS_Diag_04249)

7.6.4.3 Jump from Bootloader / ECUReset

[SWS_Dcm_00536] dAt Dcm initialization, the Dcm shall call Dcm_GetProgCondi-

tions to know if the initialization is the consequence of a jump from the bootloader /
ECUReset.c(RS_Diag_04098)

221 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Note: It is the responsibility of the software integrator to ensure that the data contained
in Dcm_ProgConditionsType is valid when Dcm_Init is called. E.g. if this data is
stored in non-volatile memory, it may take some time to make it available after an ECU
reset. This has to be taken into account when designing the ECU’s startup process.
[SWS_Dcm_00537] dIf the initialization of the Dcm is the consequence of a jump
from the bootloader / ECUReset (see [SWS_Dcm_00536], the Dcm shall call
ComM_DCM_ActiveDiagnostic(NetworkId) to request the ComManager for the full
communication mode.c()
[SWS_Dcm_00767] dWhen the ComM reports full communication to the Dcm, the Dcm
shall send the Response to the Service Id passed in the Dcm_ProgConditionsType.c
(RS_Diag_04098)
[SWS_Dcm_00768] dIf the initialization of the Dcm is the consequence of a jump
from the bootloader (see [SWS_Dcm_00536] and the application is updated by an
FLASH download (Dcm_ProgConditionsType.ApplUpdated == True), the Dcm shall call
BswM_Dcm_ApplicationUpdated() to notify the BswM that the application was up-
dated.c()

7.6.4.4 Flags management

7.6.4.4.1 Jump to Bootloader

[SWS_Dcm_01182] dOn reception of a UDS Service 0x10 request (Diagnostic Session

Control) with subfunction 0x02 (Start Programming Session), the Dcm shall set the
ReprogramingRequest flag and, if indicated for this service, the ResponseRequired
flag by calling Dcm_SetProgConditions.c()
[SWS_Dcm_01183] dDepending on configuration parameter DcmDspSessionFor-
Boot, either the application shall send the positive response (if suppressPosRspMs-
gIndicationBit = FALSE) or after an ECU reset, when the bootloader is started, it shall
send a response and clear the ResponseRequired flag. In either case, the bootloader
shall clear the ReprogramingRequest flag.c()
[SWS_Dcm_01185] dIn case that, during jump to Bootloader, the Dcm_SetProg-
Conditions API returns E_NOT_OK, a DET error shall be reported DCM_E_SET_-
PROG_CONDITIONS_FAIL and normal functionality shall resume.c()

7.6.4.4.2 Jump from Bootloader

After successful reprograming of the application software, the bootloader will update
the ApplUpdated flag and the ResponseRequired flags.

222 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

After an ECU reset, when the newly programmed application is started for the first time,
the Dcm will read the ApplUpdated and ResponseRequired flag by calling Dcm_Get-
ProgConditions. During this function call the ApplUpdated and ResponseRequired
flags are cleared by the integration code.

7.7 Error notification

The Default Error Tracer module is just help for BSW development and integration. It
must not be contained inside the production code. The API is defined, but the function-
ality can be chosen and implemented according to the development needs (e.g. errors
count, send error information via a serial interface to an external logger, and so on).

7.8 Synchronous and Asynchronous implementation

The Dcm can access data using an R-Port requiring either a synchronous or an asyn-
chronous ClientServertInterface DataServices_{Data}. In the Dcm SWS, the param-
eter DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-
DATA_ASYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR.
In case of USE_DATA_SYNCH_CLIENT_SERVER, the interface shall be compatible
with the Dem interface "DataServices_<Data>" (no OpStatus parameter). The pa-
rameter OpStatus and return parameter DCM_E_PENDING shall only be available
in case of USE_DATA_ASYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_-
SERVER_ERROR.
Note: a Dcm implementation using AsynchronousServerCallPoint or Syn-
chronousServerCallPoint when calling service processors is completely an im-
plementation decision. This only indicates that the operation uses the status of
the operation to allow an asynchronous processing by the SW-C (initiating a re-
quest, checking if a request is still pending, or canceling a pending request, see
[SWS_Dcm_00686]).
There is no correlation to the operation signature (i.e. existence of OpStatus parameter
and DCM_E_PENDING return code) that demands AsynchronousServerCallPoint or
SynchronousServerCallPoint usage.
[SWS_Dcm_01187] dIf an asynchronous interface is used, the Dcm shall consider the
Output data (OUT) only valid after the last call to the interface that returns E_OK.c()
[SWS_Dcm_01188] dIf an asynchronous interface is used, the Dcm shall consider the
OUT-parameter ErrorCode only valid after the last call to the interface that returns
E_NOT_OKc()
Note : The "last call" to the interface is the call that returns with a value that indicates
that processing has finished, i.e. E_OK or E_NOT_OK.

223 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Note : INOUT parameter are a combination of the requirements above, i.e. on each
call of the interface the parameters shall have a valid in-value, and the Dcm considers
the out-value valid only after the last call of the interface.
[SWS_Dcm_01189] dIf an asynchronous interface is used, the Dcm shall provide the
values originating from the request for the Input data (IN) on every call to the interface.c
()
Note: Requirements [SWS_Dcm_01187], [SWS_Dcm_01188] and
[SWS_Dcm_01189] do not apply for functions where a deviant behaviour is ex-
plicitly specified.

7.9 DID configuration

The configuration of the Dcm contains a list of supported DIDs which can be configured
in two ways:
• The individual DID configuration,which required one connection (either via a port
or a c-function) per configured data element of the respective DID to access to
the data (reading, writing and controlling). The interface DataServices should be
used for each DID in this case.
• The DID range configuration, used to handle a set of DIDs sharing the same
behavior uniformly in one SW-C with only one port-connection. The interface
DataServices_DIDRange_{Range} should be used in this case. Using this con-
figuration allows an interface optimization.The following parameters shall be con-
figured in order to use the DIDRange optimization: DcmDspDidRangeIdenti-
fierLowerLimit and DcmDspDidRangeIdentifierUpperLimit which de-
limited the range of the DIDs. DcmDspDidRangeMaxDataLength and DcmD-
spDidRangeHasGaps.
[SWS_Dcm_01174] dIf DcmVinRef is configured then the VIN shall be fetched once
by the Dcm during startup by calling Dcm_GetVin.c()

7.9.1 Individual DID

The individual DID can be configured in DcmDspDid. A unique DID identifier is config-
ured on 2 bytes in DcmDspDidIdentifier. In case the DID refers to other DIDs, the
link between them can be configured in DcmDspDidRef2 . Each DID allows to access
to signal data values (by reading and/or writing). The signal reference (to DcmDsp-
Data) and the position of the data in the diagnostic answer (for reading) or request (for
writing) can be configured in DcmDspDidSignal.
The configuration of the data belonging to the DID can be provided in the container
DcmDspData (ECUC_Dcm_00869). This container collects the following information:
2
Overview of DcmDspDid container is described in chapter 10.2.5.7.1

224 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• The Data endianness of the data belonging to the DID (ECUC_Dcm_00986:

DcmDspDataEndianness)
• The length and the type of the data (ECUC_Dcm_00605: DcmDspDataByte-
Size, ECUC_Dcm_00985 : DcmDspDataType)
• The interface to be used to access to the data (ECUC_Dcm_00713: DcmDsp-
DataUsePort)
• The NRAM blockId to access the data (ECUC_Dcm_00809 : DcmDspDat-
aBlockIdRef)
• The interfaces to the application in order to :
– Check if the DID can be accessed in the current conditions. This
can be achieved by checking for each DataElement if the conditions
to read the data are satisfied (ECUC_Dcm_00677: DcmDspDataCon-
ditionCheckReadFnc and ECUC_Dcm_00955: DcmDspDataCondi-
tionCheckReadFncUsed)
– Request to freeze the current state of an IOControl (ECUC_Dcm_00674:
DcmDspDataFreezeCurrentStateFnc)
– Get the scaling information of the DID. This can be achieved by getting the
scaling information for each DataElement (ECUC_Dcm_00676: DcmDsp-
DataGetScalingInfoFnc)
– Request the data length of a DataElement (ECUC_Dcm_00671: DcmDsp-
DataReadDataLengthFnc)
– Read a certain ECU signal (ECUC_Dcm_00824: DcmDspDataReadE-
cuSignal).
– Access in reading or writing to the data (ECUC_Dcm_00669 : DcmDsp-
DataReadFnc, ECUC_Dcm_00670: DcmDspDataWriteFnc)
– Request to reset an IOControl to default value (ECUC_Dcm_00673 : DcmD-
spDataResetToDefaultFnc)
– Request to return control to ECU of an IOControl (ECUC_Dcm_00672 :
DcmDspDataReturnControlToEcuFnc)
– Request to adjust the IO signal (ECUC_Dcm_00675 : DcmDspDataShort-
TermAdjustmentFnc)
It is also possible to configure an alternative diagnosis representation via
ECUC_Dcm_00993: DcmDspDiagnosisScaling.
The following example shows how to configure the containers DcmDspDid and DcmD-
spData for an individual DID 0xF080. This configuration allows access to a byte
of data via synchronous C APIs WriteDID_F080 (for writing) and ReadDID_F080 (for
reading).

225 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• DcmDspDidIdentifier=0xF080
• DcmDspDidByteOffset=0
• DcmDspDidDataRef=DcmDspData_F080
• DcmDspDataByteSize=8
• DcmDspDataType=UINT8_N
• DcmDspDataUsePort=USE_DATA_SYNCH_FNC
• DcmDspDataWriteFnc=WriteDID_F080
• DcmDspDataReadFnc=ReadDID_F080
[SWS_Dcm_CONSTR_6067] Dependency for DcmDspDataBlockIdRef dDcmD-
spDataBlockIdRef shall be only present if DcmDspDataUsePort is set to USE_-
BLOCK_ID.c()

7.9.2 DID ranges

DID ranges are in general the same as the ’normal’ DID read and write function, except
that the DID is also passed as a parameter. This allows to treat the DID range in a
switch/case in the read or the write function.
The ranges can be applied for reading (ReadDataByIdentifier 0x22) and writing (Write-
DataByIdentifier 0x2E) DIDs.
The ranges can be configured in ECUC_Dcm_00937 : DcmDspDidRange. Each con-
figured range is by default accessible by service 0x22 and 0x2E. In case the range
should be limited to reading or writing, the referenced DcmDspDidInfo container
should be defined accordingly.
It is also possible to define gaps within the range (DcmDspDidRangeHasGaps). By
activating this feature, the Dcm invokes each time a DID is requested within the config-
ured range, the operation IsDidAvailable has to check the current availability. And as
the DIDs of the specified range can have different length, the length of the longest DID
has to be configured (DcmDspDidRangeMaxDataLength) in order to reserve enough
buffer passed to the respective function.
In general, the range functionality can also be used for a single DID if you specifically
want to pass the DID as a parameter. Then lower DID and upper DID should be the
same.
ReadDidRangeDataLength operation allows to request the application to return the
data length of a DID Range.
[SWS_Dcm_CONSTR_6020] Definition of allowed DID access dAny defined range
shall only reference via DcmDspDidRangeInfoRef. The sub-containers DcmDsp-
DidControl and DcmDspDidDefineinDcmDspDidInfo shall not be used] .c()

226 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_CONSTR_6021] DID ranges cannot be mapped on DDDIDs, be-

cause service 0x2C DDDID does not support the range feature. Practi-
cally DcmDspDidRangeIdentifierLowerLimit and DcmDspDidRangeIdenti-
fierUpperLimit should not include DIDs of the range 0xF200 till 0xF3FF. dAny
defined range shall only reference DcmDspDidInfo via DcmDspDidRangeInfoRef,
having set DcmDspDidDynamicallyDefined == False.c()

7.10 Startup behavior

[SWS_Dcm_00334] dDcm_Init shall initialize all Dcm global variables with the values
of the configurationc()

8 API specification
This section defines:
• The syntax and semantics of the functions that are provided and required from
other BSW modules. These take the form of "C"-APIs.
• The syntax and semantics of a subset of those functions which are used by
software-components through the RTE. These take the form of descriptions using
the concepts of the Software-Component Template.

8.1 Imported types

In this chapter all types included from the following files are listed.
[SWS_Dcm_00333] d
Module Header File Imported Type
BndM bndm.h BndM_BlockIdType
bndm.h BndM_ResultType
bndm_externals.h BndM_Block{BlockId.Shortname}Type
ComStack_Types.h BufReq_ReturnType
ComStack_Types.h NetworkHandleType
ComStack_Types.h PduIdType
ComStack_Types.h PduInfoType
ComStack_Types.h PduLengthType
ComStack_Types.h RetryInfoType
5

227 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Module Header File Imported Type
ComStack_Types.h TpDataStateType

Dem Dem.h Dem_DTCRequestType

Dem.h Dem_DTCSeverityType
Dem.h Dem_DTCTranslationFormatType
Rte_Dem_Type.h Dem_DTCFormatType
Rte_Dem_Type.h Dem_DTCOriginType
Rte_Dem_Type.h Dem_UdsStatusByteType
IdsM IdsM_Types.h IdsM_SecurityEventIdType
KeyM Rte_KeyM_Type.h KeyM_CertificateIdType
Rte_KeyM_Type.h KeyM_CertificateStatusType
NvM Rte_NvM_Type.h NvM_BlockIdType
SchM SchM.h SchM_ReturnType
Std Std_Types.h Std_ReturnType
Std_Types.h Std_VersionInfoType

c()

8.2 Type definitions

The Dcm module shall ensure that implementation-specific types are not "visible" out-
side of Dcm. Otherwise, the complete architecture would be corrupted.
This section lists the types which are defined by the Dcm SWS.

8.2.1 Dcm_StatusType

[SWS_Dcm_00976] d
Name Dcm_StatusType
Kind Type
Derived from uint8
DCM_E_OK 0x00 This value is representing a
successful operation.
DCM_E_ROE_NOT_ACCEPTED 0x06 ResponseOnOneEvent request is
not accepted by DCM (e.g. old
ResponseOnOneEvent is not
finished) (used at API: Dcm_
ResponseOnOneEvent())
5

228 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
DCM_E_PERIODICID_NOT_ 0x07 Periodic transmission request is
ACCEPTED not accepted by DCM (e.g. old
Periodic transmission is not
finished) (used at API: Dcm_
ResponseOnOneDataByPeriodic
Id ())
Description Base item type to transport status information.
Available via Dcm.h

c()

8.2.2 Dcm_CommunicationModeType

[SWS_Dcm_00981] d
Name Dcm_CommunicationModeType
Kind Type
Derived from uint8
DCM_ENABLE_RX_TX_NORM 0x00 Enable the Rx and Tx for normal
Range
communication
DCM_ENABLE_RX_DISABLE_ 0x01 Enable the Rx and disable the Tx
TX_NORM for normal communication
DCM_DISABLE_RX_ENABLE_ 0x02 Disable the Rx and enable the Tx
TX_NORM for normal communication
DCM_DISABLE_RX_TX_ 0x03 Disable Rx and Tx for normal
NORMAL communication
DCM_ENABLE_RX_TX_NM 0x04 Enable the Rx and Tx for network
management communication
DCM_ENABLE_RX_DISABLE_ 0x05 Enable Rx and disable the Tx for
TX_NM network management
communication
DCM_DISABLE_RX_ENABLE_ 0x06 Disable the Rx and enable the Tx
TX_NM for network management
communication
DCM_DISABLE_RX_TX_NM 0x07 Disable Rx and Tx for network
management communication
DCM_ENABLE_RX_TX_NORM_ 0x08 Enable Rx and Tx for normal and
NM network management
communication
DCM_ENABLE_RX_DISABLE_ 0x09 Enable the Rx and disable the Tx
TX_NORM_NM for normal and network
management communication
DCM_DISABLE_RX_ENABLE_ 0x0A Disable the Rx and enable the Tx
TX_NORM_NM for normal and network
management communication
DCM_DISABLE_RX_TX_NORM_ 0x0B Disable Rx and Tx for normal and
NM network management
communication
Description –
5

229 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Available via Dcm.h

c()

8.2.3 Dcm_ConfigType

[SWS_Dcm_00982] d
Name Dcm_ConfigType
Kind Structure
Elements Implementation specific
Type –
Comment –
Description This type defines a data structure for the post build parameters of the DCM . At initialization the
DCM gets a pointer to a structure of this type to get access to its configuration data, which is
necessary for initialization.
Available via Dcm.h

c()

8.2.4 Dcm_ReturnReadMemoryType

[SWS_Dcm_00985] d
Name Dcm_ReturnReadMemoryType
Kind Type
Derived from uint8
Range DCM_READ_OK 0x00 Reading has been done
DCM_READ_PENDING 0x01 Reading is pending, another call
is request to finalize the reading
DCM_READ_FAILED 0x02 Reading has failed
DCM_READ_FORCE_RCRRP 0x03 Reading is pending, the
Response pending transmission
starts immediately
Description Return values of Callout Dcm_ReadMemory
Available via Dcm.h

c()

8.2.5 Dcm_ReturnWriteMemoryType

[SWS_Dcm_00986] d

230 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name Dcm_ReturnWriteMemoryType
Kind Type
Derived from uint8
Range DCM_WRITE_OK 0x00 Writing has been done
DCM_WRITE_PENDING 0x01 Writing is pending, another called
is requested
DCM_WRITE_FAILED 0x02 The writing has failed
DCM_WRITE_FORCE_RCRRP 0x03 Writing is pending, the Response
pending transmission starts
immediately
Description Return type of callout Dcm_WriteMemory
Available via Dcm.h

c()

8.2.6 Dcm_EcuStartModeType

[SWS_Dcm_00987] d
Name Dcm_EcuStartModeType
Kind Type
Derived from uint8
Range DCM_COLD_START 0x00 The ECU starts normally
DCM_WARM_START 0x01 The ECU starts from a bootloader
jump
Description Allows the DCM to know if a diagnostic response shall be sent in the case of a jump from
bootloader
Available via Dcm.h

c()

8.2.7 Dcm_ProgConditionsType

[SWS_Dcm_00988] d
Name Dcm_ProgConditionsType
Kind Structure
ConnectionId
Type uint16
Comment Unique id of the connection on which the request has been received
TesterAddress
Type uint16
5

231 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Comment Source address of the received request if meta data is enabled,
otherwise the value as configured in DcmDslProtocolRxTesterSource
Addr
Sid
Type uint8
Comment Service identifier of the received request
SubFncId
Type uint8
Comment Identifier of the received subfonction
ReprogramingRequest
Type boolean
Comment Set to true in order to request reprogramming of the ECU.
ApplUpdated
Type boolean
Comment Indicate whether the application has been updated or not.
ResponseRequired
Type boolean
Comment Set to true in case the flashloader or application shall send a response.
Description Used in Dcm_SetProgConditions() to allow the integrator to store relevant information prior to
jumping to bootloader / jump due to ECUReset request.
Available via Dcm.h

c()

8.2.8 Dcm_MsgItemType

[SWS_Dcm_00989] d
Name Dcm_MsgItemType
Kind Type
Derived from uint8
Description Base type for diagnostic message item
Available via Dcm.h

c()

8.2.9 Dcm_MsgType

[SWS_Dcm_00990] d

232 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name Dcm_MsgType
Kind Pointer
Type Dcm_MsgItemType*
Description Base type for diagnostic message (request, positive or negative response)
Available via Dcm.h

c()

8.2.10 Dcm_MsgLenType

[SWS_Dcm_00991] d
Name Dcm_MsgLenType
Kind Type
Derived from uint32
Description Length of diagnostic message (request, positive or negative response). The maximum length is
dependent of the underlying transport protocol/media.
Available via Dcm.h

c()

8.2.11 Dcm_MsgAddInfoType

Please note that the following table describes a struct type definition - including its
struct items "elements".
[SWS_Dcm_00992] d
Name Dcm_MsgAddInfoType
Kind Structure
Elements reqType
Type bit
Comment (Pos LSB+0)
0 = physical request
1 = functional request
suppressPosResponse
Type bit
Comment Position LSB+1
0 = no (do not suppress)
1 = yes (no positive response will be sent)
5

233 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Description Additional information on message request.
Datastructure: Bitfield
Available via Dcm.h

c()

8.2.12 Dcm_IdContextType

[SWS_Dcm_00993] d
Name Dcm_IdContextType
Kind Type
Derived from uint8
Description This message context identifier can be used to determine the relation between request and
response confirmation.
Available via Dcm.h

c()

8.2.13 Dcm_MsgContextType

Please note that the following table describes a struct type definition - including its
struct items "elements".
[SWS_Dcm_00994] d
Name Dcm_MsgContextType
Kind Structure
reqData
Type Dcm_MsgType
Comment Request data, starting directly after service identifier (which is not part
of this data)
reqDataLen
Type Dcm_MsgLenType
Comment Request data length (excluding service identifier)
resData
Type Dcm_MsgType
Comment Positive response data, starting directly after service identifier (which is
not part of this data).
resDataLen
Type Dcm_MsgLenType
5

234 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Comment Positive response data length (excluding service identifier)
msgAddInfo
Type Dcm_MsgAddInfoType
Comment Additional information about service request and response (see: Dcm_
MsgAddInfo)
resMaxDataLen
Type Dcm_MsgLenType
Comment The maximal length of a response is restricted by the size of the buffer.
The buffer size can depend on the diagnostic protocol identifier which
is assigned to this message, e. g. an OBD protocol id can obtain other
properties than the enhanced diagnostic protocol id. The resMaxData
Len is a property of the diagnostic protocol assigned by the DSL. The
value does not change during communication. It cannot be
implemented as a constant, because it can differ between different
diagnostic protocols.
idContext
Type Dcm_IdContextType
Comment This message context identifier can be used to determine the relation
between request and response confirmation. This identifier can be
stored within the application at request time, so that the response can
be assigned to the original request. Background: Within the
confirmation, the message context is no more valid, all message data
is lost. You need an additional information to determine the request to
which this confirmation belongs.
dcmRxPduId:
Type PduIdType
Comment Pdu identifier on which the request was received. The PduId of the
request can have consequences for message processing. E. g. an
OBD request will be received on the OBD PduId and will be processed
slightly different than an enhanced diagnostic request received on the
physical
Description This data structure contains all information which is necessary to process a diagnostic message
from request to response and response confirmation.
Available via Dcm.h

c()

8.2.14 Dcm_ExtendedOpStatusType

[SWS_Dcm_91015] d
Name Dcm_ExtendedOpStatusType
Kind Type
Derived from uint8
DCM_INITIAL 0x00 Indicates the initial call to the
operation
DCM_PENDING 0x01 Indicates that a pending return
has been done on the previous
call of the operation
5

235 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
DCM_CANCEL 0x02 Indicates that the Dcm requests to
cancel the pending operation
DCM_FORCE_RCRRP_OK 0x03 Confirm a response pending
transmission Variation
DCM_POS_RESPONSE_SENT 0x04 Indicates that a positive response
has been sent successfully
DCM_POS_RESPONSE_FAILED 0x05 Indicates that a positive response
has not been sent successfully
DCM_NEG_RESPONSE_SENT 0x06 Indicates that a negative response
has been sent successfully
DCM_NEG_RESPONSE_FAILED 0x07 Indicates that a negative response
has not been sent successfully
Description –
Available via Dcm.h

c()

8.3 Function definitions

This section defines the functions provided for other modules.

8.3.1 Functions provided for other BSW components

8.3.1.1 Dcm_Init

[SWS_Dcm_00037] d
Service Name Dcm_Init
Syntax void Dcm_Init (
const Dcm_ConfigType* ConfigPtr
)

Service ID [hex] 0x01

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) ConfigPtr Pointer to configuration set in Variant Post-Build.
Parameters (inout) None
Parameters (out) None
Return value None
Description Service for basic initialization of DCM module.
Available via Dcm.h

c(SRS_BSW_00438, SRS_BSW_00101)
The call of this service is mandatory before using the Dcm module for further process-
ing.

236 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.3.1.2 Dcm_GetVersionInfo

[SWS_Dcm_00065] d
Service Name Dcm_GetVersionInfo
Syntax void Dcm_GetVersionInfo (
Std_VersionInfoType* versionInfo
)

Service ID [hex] 0x24

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) versionInfo Pointer to where to store the version information of this module.
Return value None
Description Returns the version information of this module
Available via Dcm.h

c(SRS_BSW_00407, SRS_BSW_00482, SRS_BSW_00003)

8.3.1.3 Dcm_DemTriggerOnDTCStatus

[SWS_Dcm_00614] d
Service Name Dcm_DemTriggerOnDTCStatus
Syntax Std_ReturnType Dcm_DemTriggerOnDTCStatus (
uint32 DTC,
Dem_UdsStatusByteType DTCStatusOld,
Dem_UdsStatusByteType DTCStatusNew
)

Service ID [hex] 0x2B

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) DTC This is the DTC the change trigger is assigned to.
DTCStatusOld DTC status before change
DTCStatusNew DTC status after change
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: this value is always returned.
Description Triggers on changes of the UDS status byte. Allows to trigger on ROE Event for subservice On
DTCStatusChanged.
Available via Dcm_Dem.h

c()

237 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.3.1.4 Dcm_GetVin

[SWS_Dcm_00950] d
Service Name Dcm_GetVin
Syntax Std_ReturnType Dcm_GetVin (
uint8* Data
)

Service ID [hex] 0x07

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) Data Pointer to where to store the VIN
Return value Std_ReturnType E_OK: The Data pointer has been filled with valid VIN
E_NOT_OK: The default VIN will be used in the DoIP
Description Function to get the VIN (as defined in SAE J1979-DA)
Available via Dcm.h

c()
Note: After fetching the VIN, the Dcm can offer the data to all users without worrying
that the data is unavailable if a user asks for it. This is necessary because the VIN
could not be fetched synchronously for all settings of DcmDspDidDataUsePort.

8.3.1.5 Dcm_BndMWriteBlockFinish

[SWS_Dcm_91088] d
Service Name Dcm_BndMWriteBlockFinish
Syntax void Dcm_BndMWriteBlockFinish (
BndM_BlockIdType BlockId,
BndM_ResultType result
)

Service ID [hex] 0x7a

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) BlockId –
result –
Parameters (inout) None
Parameters (out) None
Return value None
Description Called by BndM to indicate that a block write operation has finished.
Available via Dcm.h

c(RS_Diag_04243)

238 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.3.2 Functions provided to BSW modules and to SW-Cs

The functions defined in this section can also be used by SW-Cs through the RTE.

8.3.2.1 Dcm_SetDeauthenticatedRole

[SWS_Dcm_91069] d
Service Name Dcm_SetDeauthenticatedRole
Syntax Std_ReturnType Dcm_SetDeauthenticatedRole (
uint16 connectionId,
Dcm_AuthenticationRoleType deauthenticatedRole
)

Service ID [hex] 0x79

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) connectionId Unique connection identifier identifiying the connection for which
a deauthenticated roles is set.
deauthenticatedRole New deauthenticated role that is assigned to that connection
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: this value is always returned.
Description Sets a new role used in deauthenticated state for that connection. The set role is valid until the
connection switches into authenticated state or the ECU is reset.
Available via Dcm.h

c()

8.3.2.2 Dcm_GetSecurityLevel

[SWS_Dcm_00338] d
Service Name Dcm_GetSecurityLevel
Syntax Std_ReturnType Dcm_GetSecurityLevel (
Dcm_SecLevelType* SecLevel
)

Service ID [hex] 0x0d

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) None
Parameters (inout) None
5

239 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Parameters (out) SecLevel Active Security Level value Conversion formula to calculate
SecurityLevel out of tester requested SecurityAccessType
parameter: SecurityLevel = (SecurityAccessType + 1) / 2 Content
of SecurityAccessType is according to "securityAccessType"
parameter of SecurityAccess request (see [11])
Return value Std_ReturnType E_OK: this value is always returned.
Description This function provides the active security level value.
Available via Dcm.h

c(RS_Diag_04005, RS_Diag_04011)

8.3.2.3 Dcm_GetSesCtrlType

[SWS_Dcm_00339] d
Service Name Dcm_GetSesCtrlType
Syntax Std_ReturnType Dcm_GetSesCtrlType (
Dcm_SesCtrlType* SesCtrlType
)

Service ID [hex] 0x06

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) SesCtrlType Active Session Control Type value Content is according to
"diagnosticSessionType" parameter of DiagnosticSessionControl
request (see [11])
Return value Std_ReturnType E_OK: this value is always returned.
Description This function provides the active session control type value.
Available via Dcm.h

c(RS_Diag_04006, RS_Diag_04011)

8.3.2.4 Dcm_GetActiveProtocol

[SWS_Dcm_00340] d
Service Name Dcm_GetActiveProtocol
Syntax Std_ReturnType Dcm_GetActiveProtocol (
Dcm_ProtocolType* ActiveProtocolType,
uint16* ConnectionId,
uint16* TesterSourceAddress
)
5

240 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Service ID [hex] 0x0f
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) ActiveProtocolType Active protocol type value
ConnectionId Unique connection identifier
TesterSourceAddress source address of the tester
Return value Std_ReturnType E_OK: this value is always returned.
Description This function returns the active UDS protocol details
Available via Dcm.h

c(RS_Diag_04011)

8.3.2.5 Dcm_ResetToDefaultSession

[SWS_Dcm_00520] d
Service Name Dcm_ResetToDefaultSession
Syntax Std_ReturnType Dcm_ResetToDefaultSession (
void
)

Service ID [hex] 0x2a

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: this value is always returned.
Description The call to this function allows the application to reset the current session to Default session.
Example: Automatic termination of an extended diagnostic session upon exceeding of a speed
limit.
Available via Dcm.h

c()

8.3.2.6 Dcm_TriggerOnEvent

[SWS_Dcm_00521] d

241 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Dcm_TriggerOnEvent

Syntax Std_ReturnType Dcm_TriggerOnEvent (
uint8 RoeEventId
)

Service ID [hex] 0x2D

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) RoeEventId Identifier of the event that is triggered
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: RoeEventId value is valid
E_NOT_OK: RoeEventId value is not valid
Description The call to this function allows to trigger an event linked to a ResponseOnEvent request. On the
function call, the DCM will execute the associated service if the corresponding Mode of the Roe
EventId is ’ROE started’.
Available via Dcm.h

c()

8.3.2.7 Dcm_ SetActiveDiagnostic

[SWS_Dcm_01068] d
Service Name Dcm_SetActiveDiagnostic
Syntax Std_ReturnType Dcm_SetActiveDiagnostic (
boolean active
)

Service ID [hex] 0x56

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) active If false Dcm shall not call ComM_DCM_ActiveDiagnostic(). If true
Dcm will call ComM_DCM_ActiveDiagnostic().
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: this value is always returned.
Description Allows to activate and deactivate the call of ComM_DCM_ActiveDiagnostic() function.
Available via Dcm.h

c()

8.4 Callback notifications

This section defines the functions provided for lower layer BSW modules.

242 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

class DCMCallbacks

«module»
Dcm

«realize» «realize»

«interface» «interface»
Dcm_PduR Dcm_ComM

Dcm_CopyRxData() Dcm_ComMNoComModeEntered()
Dcm_CopyTxData() Dcm_ComMSilentComModeEntered()
Dcm_RxIndication() Dcm_ComMFullComModeEntered()
Dcm_TxConfirmation()
Dcm_StartOfReception()

«optional»

«module»
«module»
__PduR
ComM

Figure 8.1: Overview of the callbacks provided by the DCM

8.4.1 Dcm_StartOfReception

[SWS_Dcm_00094] d
Service Name Dcm_StartOfReception
Syntax BufReq_ReturnType Dcm_StartOfReception (
PduIdType id,
const PduInfoType* info,
PduLengthType TpSduLength,
PduLengthType* bufferSizePtr
)

Service ID [hex] 0x46

Sync/Async Synchronous
Reentrancy Reentrant
5

243 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Parameters (in) id Identification of the I-PDU.
info Pointer to a PduInfoType structure containing the payload data
(without protocol information) and payload length of the first
frame or single frame of a transport protocol I-PDU reception, and
the MetaData related to this PDU. If neither first/single frame data
nor MetaData are available, this parameter is set to NULL_PTR.
TpSduLength Total length of the N-SDU to be received.
Parameters (inout) None
Parameters (out) bufferSizePtr Available receive buffer in the receiving module. This parameter
will be used to compute the Block Size (BS) in the transport
protocol module.
Return value BufReq_ReturnType BUFREQ_OK: Connection has been accepted. bufferSizePtr
indicates the available receive buffer; reception is continued. If no
buffer of the requested size is available, a receive buffer size of 0
shall be indicated by bufferSizePtr.
BUFREQ_E_NOT_OK: Connection has been rejected; reception
is aborted. bufferSizePtr remains unchanged.
BUFREQ_E_OVFL: No buffer of the required length can be
provided; reception is aborted. bufferSizePtr remains unchanged.
Description This function is called at the start of receiving an N-SDU. The N-SDU might be fragmented into
multiple N-PDUs (FF with one or more following CFs) or might consist of a single N-PDU (SF).
The service shall provide the currently available maximum buffer size when invoked with TpSdu
Length equal to 0. This function might be called in interrupt context.
Available via Dcm.h

c()
By the function Dcm_StartOfReception the receiver (e.g. DCM) is also informed
implicitly about a first frame reception or a single frame reception. If the function Dcm_-
StartOfReception returns a return value not equal to BUFREQ_OK, the values of
the out parameters are not specified and should not be evaluated by the caller.

8.4.2 Dcm_CopyRxData

[SWS_Dcm_00556] d
Service Name Dcm_CopyRxData
Syntax BufReq_ReturnType Dcm_CopyRxData (
PduIdType id,
const PduInfoType* info,
PduLengthType* bufferSizePtr
)

Service ID [hex] 0x44

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) id Identification of the received I-PDU.
5

244 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
info Provides the source buffer (SduDataPtr) and the number of bytes
to be copied (SduLength). An SduLength of 0 can be used to
query the current amount of available buffer in the upper layer
module. In this case, the SduDataPtr may be a NULL_PTR.
Parameters (inout) None
Parameters (out) bufferSizePtr Available receive buffer after data has been copied.
Return value BufReq_ReturnType BUFREQ_OK: Data copied successfully
BUFREQ_E_NOT_OK: Data was not copied because an error
occurred.
Description This function is called to provide the received data of an I-PDU segment (N-PDU) to the upper
layer. Each call to this function provides the next part of the I-PDU data. The size of the
remaining buffer is written to the position indicated by bufferSizePtr. This function might be
called in interrupt context.
Available via Dcm.h

c()

8.4.3 Dcm_TpRxIndication

[SWS_Dcm_00093] d
Service Name Dcm_TpRxIndication
Syntax void Dcm_TpRxIndication (
PduIdType id,
Std_ReturnType result
)

Service ID [hex] 0x45

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) id Identification of the received I-PDU.
result Result of the reception.
Parameters (inout) None
Parameters (out) None
Return value None
Description Called after an I-PDU has been received via the TP API, the result indicates whether the
transmission was successful or not. This function might be called in interrupt context.
Available via Dcm.h

c()

8.4.4 Dcm_CopyTxData

[SWS_Dcm_00092] d

245 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Dcm_CopyTxData

Syntax BufReq_ReturnType Dcm_CopyTxData (
PduIdType id,
const PduInfoType* info,
const RetryInfoType* retry,
PduLengthType* availableDataPtr
)

Service ID [hex] 0x43

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) id Identification of the transmitted I-PDU.
info Provides the destination buffer (SduDataPtr) and the number of
bytes to be copied (SduLength). If not enough transmit data is
available, no data is copied by the upper layer module and
BUFREQ_E_BUSY is returned. The lower layer module may
retry the call. An SduLength of 0 can be used to indicate state
changes in the retry parameter or to query the current amount of
available data in the upper layer module. In this case, the Sdu
DataPtr may be a NULL_PTR.
retry This parameter is used to acknowledge transmitted data or to
retransmit data after transmission problems.
If the retry parameter is a NULL_PTR, it indicates that the
transmit data can be removed from the buffer immediately after it
has been copied. Otherwise, the retry parameter must point to a
valid RetryInfoType element.
If TpDataState indicates TP_CONFPENDING, the previously
copied data must remain in the TP buffer to be available for error
recovery. TP_DATACONF indicates that all data that has been
copied before this call is confirmed and can be removed from the
TP buffer. Data copied by this API call is excluded and will be
confirmed later. TP_DATARETRY indicates that this API call shall
copy previously copied data in order to recover from an error. In
this case TxTpDataCnt specifies the offset in bytes from the
current data copy position.
Parameters (inout) None
Parameters (out) availableDataPtr Indicates the remaining number of bytes that are available in the
upper layer module’s Tx buffer. availableDataPtr can be used by
TP modules that support dynamic payload lengths (e.g. FrIsoTp)
to determine the size of the following CFs.
Return value BufReq_ReturnType BUFREQ_OK: Data has been copied to the transmit buffer
completely as requested.
BUFREQ_E_BUSY: Request could not be fulfilled, because the
required amount of Tx data is not available. The lower layer
module may retry this call later on. No data has been copied.
BUFREQ_E_NOT_OK: Data has not been copied. Request
failed.
Description This function is called to acquire the transmit data of an I-PDU segment (N-PDU). Each call to
this function provides the next part of the I-PDU data unless retry->TpDataState is TP_
DATARETRY. In this case the function restarts to copy the data beginning at the offset from the
current position indicated by retry->TxTpDataCnt. The size of the remaining data is written to
the position indicated by availableDataPtr. This function might be called in interrupt context.
Available via Dcm.h

c()

246 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.4.5 Dcm_TpTxConfirmation

[SWS_Dcm_00351] d
Service Name Dcm_TpTxConfirmation
Syntax void Dcm_TpTxConfirmation (
PduIdType id,
Std_ReturnType result
)

Service ID [hex] 0x48

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) id Identification of the transmitted I-PDU.
result Result of the transmission of the I-PDU.
Parameters (inout) None
Parameters (out) None
Return value None
Description This function is called after the I-PDU has been transmitted on its network, the result indicates
whether the transmission was successful or not. This function might be called in interrupt
context.
Available via Dcm.h

c()

8.4.6 Dcm_TxConfirmation

[SWS_Dcm_01092] d
Service Name Dcm_TxConfirmation
Syntax void Dcm_TxConfirmation (
PduIdType TxPduId,
Std_ReturnType result
)

Service ID [hex] 0x40

Sync/Async Synchronous
Reentrancy Reentrant for different PduIds. Non reentrant for the same PduId.
Parameters (in) TxPduId ID of the PDU that has been transmitted.
result E_OK: The PDU was transmitted. E_NOT_OK: Transmission of
the PDU failed.
Parameters (inout) None
Parameters (out) None
Return value None
Description The lower layer communication interface module confirms the transmission of a PDU, or the
failure to transmit a PDU. This function might be called in interrupt context.
Available via Dcm.h

c()

247 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.4.7 Dcm_ComM_NoComModeEntered

[SWS_Dcm_00356] d
Service Name Dcm_ComM_NoComModeEntered
Syntax void Dcm_ComM_NoComModeEntered (
uint8 NetworkId
)

Service ID [hex] 0x21

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) NetworkId Identifier of the network concerned by the mode change
Parameters (inout) None
Parameters (out) None
Return value None
Description This call informs the Dcm module about a ComM mode change to COMM_NO_
COMMUNICATION.
Available via Dcm_ComM.h

c()

8.4.8 Dcm_ComM_SilentComModeEntered

[SWS_Dcm_00358] d
Service Name Dcm_ComM_SilentComModeEntered
Syntax void Dcm_ComM_SilentComModeEntered (
uint8 NetworkId
)

Service ID [hex] 0x22

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) NetworkId Identifier of the network concerned by the mode change
Parameters (inout) None
Parameters (out) None
Return value None
Description This call informs the Dcm module about a ComM mode change to COMM_SILENT_
COMMUNICATION.
Available via Dcm_ComM.h

c()

8.4.9 Dcm_ComM_FullComModeEntered

[SWS_Dcm_00360] d

248 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Dcm_ComM_FullComModeEntered

Syntax void Dcm_ComM_FullComModeEntered (
uint8 NetworkId
)

Service ID [hex] 0x23

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) NetworkId Identifier of the network concerned by the mode change
Parameters (inout) None
Parameters (out) None
Return value None
Description This call informs the Dcm module about a ComM mode change to COMM_FULL_
COMMUNICATION.
Available via Dcm_ComM.h

c()

8.4.10 Dcm_CsmAsyncJobFinished

[SWS_Dcm_91076] d
Service Name Dcm_CsmAsyncJobFinished
Syntax Std_ReturnType Dcm_CsmAsyncJobFinished (
Csm_ResultType result
)

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) result Return value of the asynchronous job
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: this value is always returned.
Description Can be called from Csm upon finishing an asynchronous job processing. The integrator will
configure this name as callback function within the Csm ECUC configuration for asynchronous
jobs. Only one such callback is available, the Dcm detects the job that has finished by
evaluating the job parameter. API availability: This API will be available only if ({ecuc(Dcm/Dcm
Dsp/DcmDspAuthentication/DcmDspAuthenticationConnection} != null).
Available via

c()

8.4.11 Dcm_KeyMAsyncCertificateVerifyFinished

[SWS_Dcm_91077] d

249 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Dcm_KeyMAsyncCertificateVerifyFinished

Syntax Std_ReturnType Dcm_KeyMAsyncCertificateVerifyFinished (
KeyM_CertificateIdType CertID,
KeyM_CertificateStatusType Result
)

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) CertID Certificate identifier that has finished the verification
Result Return value of the asynchronous job
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: this value is always returned
Description Can be called from Key upon finishing an asynchronous certificate verification. The integrator
will configure this name as callback function within the KeyM ECUC configuration for
asynchronous jobs. Only one such callback is available, the Dcm detects the certificate that has
finished by evaluating the certId parameter. API availability: This API will be available only if
({ecuc(Dcm/DcmDsp/DcmDspAuthentication/DcmDspAuthenticationConnection} != null).
Available via

c()

8.5 Callout Definitions

Callouts are pieces of code that have to be added to the Dcm during ECU integra-
tion. The content of most callouts is hand-written code, for some callouts the Dcm
configuration tool shall generate a default implementation that is manually edited by
the integrator. Conceptually, these callouts belong to the ECU Firmware.
Since callouts are no services of the Dcm they do not have an assigned Service ID.
Note: The Autosar architecture doesn’t provide the possibility to access the ECU mem-
ory using a physical address. This realized using BlockId which identified a memory
block.
According to that, the Dcm is not able to fully support the implementation of ISO14229-
1 [1]services which request a physical memory access. Therefore, the Dcm define
callout to realize this kind of memory access. This callout implementation could be
simply realized by defining a mapping between the BlockId and the physical memory
address.

8.5.1 Dcm_ReadMemory

[SWS_Dcm_00539] d

250 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Dcm_ReadMemory

Syntax Dcm_ReturnReadMemoryType Dcm_ReadMemory (
Dcm_OpStatusType OpStatus,
uint8 MemoryIdentifier,
uint32 MemoryAddress,
uint32 MemorySize,
uint8* MemoryData,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x26

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_FORCE_
RCRRP_OK
MemoryIdentifier Identifier of the Memory Block (e.g. used if memory section
distinguishing is needed) Note: If it’s not used this parameter
shall be set to 0.
MemoryAddress Starting address of server memory from which data is to be
retrieved.
MemorySize Number of bytes in the MemoryData
Parameters (inout) None
Parameters (out) MemoryData Data read (Points to the diagnostic buffer in DCM)
ErrorCode If the operation Dcm_ReadMemory returns value DCM_READ_
FAILED, the Dcm module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Dcm_ReturnRead DCM_READ_OK: read was successful
MemoryType DCM_READ_FAILED: read was not successful
DCM_READ_PENDING: read is not yet finished
DCM_READ_FORCE_RCRRP: reading is pending, the
Response pending transmission starts immediately
Description The Dcm_ReadMemory callout is used to request memory data identified by the parameter
memoryAddress and memorySize from the UDS request message. This service is needed for
the implementation of UDS services:
• ReadMemoryByAddress
• RequestUpload
• ReadDataByIdentifier (in case of Dynamical DID defined by memory address)
• TransferData
Available via Dcm_Externals.h

c()

8.5.2 Dcm_WriteMemory

[SWS_Dcm_00540] d

251 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Dcm_WriteMemory

Syntax Dcm_ReturnWriteMemoryType Dcm_WriteMemory (
Dcm_OpStatusType OpStatus,
uint8 MemoryIdentifier,
uint32 MemoryAddress,
uint32 MemorySize,
const uint8* MemoryData,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x27

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_FORCE_
RCRRP_OK
MemoryIdentifier Identifier of the Memory Block (e.g. used by WriteDataByIdentifier
service). Note: If it’s not used this parameter shall be set to 0.
MemoryAddress Starting address of server memory in which data is to be copied.
Note: If it’s not used (e.g. if the data is compressed) this
parameter shall be set to 0.
MemorySize Number of bytes in MemoryData
MemoryData Data to write (Points to the diagnostic buffer in DCM)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Dcm_WriteMemory returns value DCM_WRITE_
FAILED, the Dcm module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Dcm_ReturnWrite DCM_WRITE_OK: write was successful
MemoryType DCM_WRITE_FAILED: write was not successful
DCM_WRITE_PENDING: write is not yet finished
DCM_WRITE_FORCE_RCRRP: writing is pending, the
Response pending transmission starts immediately
Description The Dcm_WriteMemory callout is used to write memory data identified by the parameter
memoryAddress and memorySize. This service is needed for the implementation of UDS
services :
• WriteMemoryByAddress
• RequestDownload
• TransferData
Available via Dcm_Externals.h

c()
Note : The callout implementation shall take care of the following points :
• When writing data in NVRAM, take care to keep the consistency with data in the
mirror RAM
• When writing data in memory, take care that a SW-C won’t overwrite the data.
Maybe the SW-C should be informed of this writing

8.5.3 Dcm_SetProgConditions

[SWS_Dcm_00543] d

252 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Dcm_SetProgConditions

Syntax Std_ReturnType Dcm_SetProgConditions (
Dcm_OpStatusType OpStatus,
const Dcm_ProgConditionsType* ProgConditions
)

Service ID [hex] 0x61

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_
FORCE_RCRRP_OK
ProgConditions Conditions on which the jump to bootloader has been requested
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: Conditions have correctly been set
E_NOT_OK: Conditions cannot be set
DCM_E_PENDING: Conditions set is in progress, a further call to
this API is needed to end the setting
DCM_E_FORCE_RCRRP: Application requests the transmission
of a response Response Pending (NRC 0x78)
Description The Dcm_SetProgConditions callout allows the integrator to store relevant information prior to
jumping to bootloader / jump due to ECUReset request. The context parameter are defined in
Dcm_ProgConditionsType.
Available via Dcm_Externals.h

c()
Note: In case the SecurityAccess AttemptCounter needs to be shared between appli-
cation and bootloader in addition to the ProgConditionStructure the current value can
be retrieved via the API Xxx_GetSecurityAttemptCounter (see chapter 7.6.4 In-
teraction)

8.5.4 Dcm_GetProgConditions

[SWS_Dcm_00544] d
Service Name Dcm_GetProgConditions
Syntax Dcm_EcuStartModeType Dcm_GetProgConditions (
Dcm_ProgConditionsType * ProgConditions
)

Service ID [hex] 0x62

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) ProgConditions Conditions on which the jump from the bootloader has been
requested
5

253 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Return value Dcm_EcuStartModeType –
Description The Dcm_GetProgConditions callout is called upon Dcm initialization and allows to determine if
a response ($50 or $51) has to be sent. The context parameters are defined in Dcm_Prog
ConditionsType.
Available via Dcm_Externals.h

c()

8.5.5 Dcm_ProcessRequestAddFile

[SWS_Dcm_91078] d
Service Name Dcm_ProcessRequestAddFile
Syntax Std_ReturnType Dcm_ProcessRequestAddFile (
Dcm_OpStatusType OpStatus,
uint16 filePathAndNameLength,
const uint8* filePathAndName,
uint8 dataFormatIdentifier,
uint64 fileSizeUncompressed,
uint64 fileSizeCompressed,
uint64* maxNumberOfBlockLength,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x72

Sync/Async Asynchronous
Reentrancy Non Reentrant

Parameters (in) OpStatus DCM_INITIAL: All In-parameters are valid. DCM_PENDING: All
In-parameters are set to 0x00. DCM_CANCEL: All In-parameters
are set to 0x00. DCM_FORCE_RCRRP_OK: All In-parameters
are set to 0x00.
filePathAndNameLength Defines the length in bytes for the parameter filePathAndName.
filePathAndName Defines the file system location of the server where the file which
shall be added, deleted, replaced or read from depending on the
parameter modeOfOperation parameter. In addition this
parameter includes the file name of the file which shall be added,
deleted, replaced or read as part of the file path.
dataFormatIdentifier This data-parameter is a one byte value with each nibble
encoded separately. The high nibble specifies the "compression
Method", and the low nibble specifies the "encryptingMethod".
The value 0x00 specifies that neither compressionMethod nor
encryptingMethod is used. Values other than 0x00 are vehicle
manufacturer specific.
fileSizeUncompressed Defines the size of the uncompressed file to be download in
bytes.
fileSizeCompressed Defines the size of the compressed file to be downloaded in
bytes.
Parameters (inout) None
Parameters (out) maxNumberOfBlock Max number of bytes to be included in each TransferData request
Length excluding the SID and the blockSequenceCounter.
5

254 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
ErrorCode If the operation Dcm_ProcessRequestAddFile returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application request the transmission
of a response Response Pending (NRC 0x78)
Description Callout function. DCM shall call this function to start a RequestFileTransfer process with mode
OfOperation equal to 0x01 (AddFile).
Available via Dcm_Externals.h

c()

8.5.6 Dcm_ProcessRequestDeleteFile

[SWS_Dcm_91079] d
Service Name Dcm_ProcessRequestDeleteFile
Syntax Std_ReturnType Dcm_ProcessRequestDeleteFile (
Dcm_OpStatusType OpStatus,
uint16 filePathAndNameLength,
const uint8* filePathAndName,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x73

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL: All In-parameters are valid. DCM_PENDING: All
In-parameters are set to 0x00. DCM_CANCEL: All In-parameters
are set to 0x00. DCM_FORCE_RCRRP_OK: All In-parameters
are set to 0x00.
filePathAndNameLength Defines the length in bytes for the parameter filePathAndName.
filePathAndName Defines the file system location of the server where the file which
shall be added, deleted, replaced or read from depending on the
parameter modeOfOperation parameter. In addition this
parameter includes the file name of the file which shall be added,
deleted, replaced or read as part of the file path.
Parameters (inout) None
Parameters (out) ErrorCode If the operation Dcm_ProcessRequestDeleteFile returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application request the transmission
of a response Response Pending (NRC 0x78)
Description Callout function. DCM shall call this function to start a RequestFileTransfer process with mode
OfOperation equal to 0x02 (DeleteFile).
5

255 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Available via Dcm_Externals.h

c()

8.5.7 Dcm_ProcessRequestReplaceFile

[SWS_Dcm_91080] d
Service Name Dcm_ProcessRequestReplaceFile
Syntax Std_ReturnType Dcm_ProcessRequestReplaceFile (
Dcm_OpStatusType OpStatus,
uint16 filePathAndNameLength,
const uint8* filePathAndName,
uint8 dataFormatIdentifier,
uint64 fileSizeUncompressed,
uint64 fileSizeCompressed,
uint64* maxNumberOfBlockLength,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x74

Sync/Async Asynchronous
Reentrancy Non Reentrant

Parameters (in) OpStatus DCM_INITIAL: All In-parameters are valid. DCM_PENDING: All
In-parameters are set to 0x00. DCM_CANCEL: All In-parameters
are set to 0x00. DCM_FORCE_RCRRP_OK: All In-parameters
are set to 0x00.
filePathAndNameLength Defines the length in bytes for the parameter filePathAndName.
filePathAndName Defines the file system location of the server where the file which
shall be added, deleted, replaced or read from depending on the
parameter modeOfOperation parameter. In addition this
parameter includes the file name of the file which shall be added,
deleted, replaced or read as part of the file path.
dataFormatIdentifier This data-parameter is a one byte value with each nibble
encoded separately. The high nibble specifies the "compression
Method", and the low nibble specifies the "encryptingMethod".
The value 0x00 specifies that neither compressionMethod nor
encryptingMethod is used. Values other than 0x00 are vehicle
manufacturer specific.
fileSizeUncompressed Defines the size of the uncompressed file to be download in
bytes.
fileSizeCompressed Defines the size of the compressed file to be downloaded in
bytes.
Parameters (inout) None
Parameters (out) maxNumberOfBlock Max number of bytes to be included in each TransferData request
Length excluding the SID and the blockSequenceCounter.
ErrorCode If the operation Dcm_ProcessRequestReplaceFile returns value
E_NOT_OK, the DCM module shall send a negative response
with NRC code equal to the parameter ErrorCode parameter
value.
5

256 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application request the transmission
of a response Response Pending (NRC 0x78)
Description Callout function. DCM shall call this function to start a RequestFileTransfer process with mode
OfOperation equal to 0x03 (ReplaceFile).
Available via Dcm_Externals.h

c()

8.5.8 Dcm_ProcessRequestReadFile

[SWS_Dcm_91081] d
Service Name Dcm_ProcessRequestReadFile
Syntax Std_ReturnType Dcm_ProcessRequestReadFile (
Dcm_OpStatusType OpStatus,
uint16 filePathAndNameLength,
const uint8* filePathAndName,
uint8 dataFormatIdentifier,
uint64 fileSizeUncompressed,
uint64 fileSizeCompressed,
uint64* maxNumberOfBlockLength,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x75

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL: All In-parameters are valid. DCM_PENDING: All
In-parameters are set to 0x00. DCM_CANCEL: All In-parameters
are set to 0x00. DCM_FORCE_RCRRP_OK: All In-parameters
are set to 0x00.
filePathAndNameLength Defines the length in bytes for the parameter filePathAndName.
filePathAndName Defines the file system location of the server where the file which
shall be added, deleted, replaced or read from depending on the
parameter modeOfOperation parameter. In addition this
parameter includes the file name of the file which shall be added,
deleted, replaced or read as part of the file path.
dataFormatIdentifier This data-parameter is a one byte value with each nibble
encoded separately. The high nibble specifies the "compression
Method", and the low nibble specifies the "encryptingMethod".
The value 0x00 specifies that neither compressionMethod nor
encryptingMethod is used. Values other than 0x00 are vehicle
manufacturer specific.
Parameters (inout) None
fileSizeUncompressed Defines the size of the uncompressed file to be uploaded in bytes.
fileSizeCompressed Defines the size of the compressed file to be uploaded in bytes.
maxNumberOfBlock Max number of bytes to be included in each TransferData
Length response excluding the SID and the blockSequenceCounter.
5

257 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
ErrorCode If the operation Dcm_ProcessRequestReadFile returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application request the transmission
of a response Response Pending (NRC 0x78)
Description Callout function. DCM shall call this function to start a RequestFileTransfer process with mode
OfOperation equal to 0x04 (ReadFile).
Available via Dcm_Externals.h

c()

8.5.9 Dcm_ProcessRequestReadDir

[SWS_Dcm_91082] d
Service Name Dcm_ProcessRequestReadDir
Syntax Std_ReturnType Dcm_ProcessRequestReadDir (
Dcm_OpStatusType OpStatus,
uint16 filePathAndNameLength,
const uint8* filePathAndName,
uint64* dirInfoLength,
uint64* maxNumberOfBlockLength,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x76

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL: All In-parameters are valid. DCM_PENDING: All
In-parameters are set to 0x00. DCM_CANCEL: All In-parameters
are set to 0x00. DCM_FORCE_RCRRP_OK: All In-parameters
are set to 0x00.
filePathAndNameLength Defines the length in bytes for the parameter filePathAndName.
filePathAndName Defines the file system location of the server where the file which
shall be added, deleted, replaced or read from depending on the
parameter modeOfOperation parameter. In addition this
parameter includes the file name of the file which shall be added,
deleted, replaced or read as part of the file path.
Parameters (inout) None
Parameters (out) dirInfoLength Defines the size of directory information to be uploaded in bytes.
maxNumberOfBlock Max number of bytes to be included in each TransferData request
Length excluding the SID and the blockSequenceCounter.
ErrorCode If the operation Dcm_ProcessRequestReadDir returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
5

258 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application request the transmission
of a response Response Pending (NRC 0x78)
Description Callout function. DCM shall call this function to start a RequestFileTransfer process with mode
OfOperation equal to 0x05 (ReadDir).
Available via Dcm_Externals.h

c()

8.5.10 Dcm_WriteFile

[SWS_Dcm_91083] d
Service Name Dcm_WriteFile
Syntax Std_ReturnType Dcm_WriteFile (
Dcm_OpStatusType OpStatus,
uint64 DataLength,
uint8* Data,
Dcm_NegativeResponseCodeType* ErrorCode
)

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL: All In-parameters are valid. DCM_PENDING: All
In-parameters are set to 0x00. DCM_CANCEL: All In-parameters
are set to 0x00. DCM_FORCE_RCRRP_OK: All In-parameters
are set to 0x00.
DataLength Defines the length in bytes for the parameter Data. The value will
not exceed, but might be less, compared to the value of max
NumberOfBlockLength return in Dcm_ProcessRequestFile
Transfer.
Data Pointer to the data to be written.
Parameters (inout) None
Parameters (out) ErrorCode If the operation Dcm_WriteFile returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application request the transmission
of a response Response Pending (NRC 0x78)
Description Callout function. DCM shall call this function when data is received using UDS service Transfer
Data if there’s an ongoing RequestFileTransfer process started with 0x01 (AddFile) or 0x03
(ReplaceFile).
Available via Dcm_Externals.h

c()

259 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.5.11 Dcm_ReadFileOrDir

[SWS_Dcm_91085] d
Service Name Dcm_ReadFileOrDir
Syntax Std_ReturnType Dcm_ReadFileOrDir (
Dcm_OpStatusType OpStatus,
uint64* DataLength,
uint8* Data,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x78

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL: All In-parameters are valid. DCM_PENDING: All
In-parameters are set to 0x00. DCM_CANCEL: All In-parameters
are set to 0x00. DCM_FORCE_RCRRP_OK: All In-parameters
are set to 0x00.
Data Pointer to the data to be written.
Parameters (inout) DataLength As in, the parameter defines the maximum block length to be
used, i.e. the value of maxNumberOfBlockLength sent to the
client in the response of RequestFileTransfer.
As out, the parameter defines the actual length in bytes for the
parameter Data. The value shall not exceed, but might be less,
the value provided as in parameter.
Parameters (out) ErrorCode If the operation Dcm_ReadFileOrDir returns value E_NOT_OK,
the DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application request the transmission
of a response Response Pending (NRC 0x78)
Description Callout function. DCM shall call this function when data shall be sent as a response to UDS
service TransferData if there’s an ongoing RequestFileTransfer process started with 0x04
(ReadFile) or 0x05 (ReadDir).
Available via Dcm_Externals.h

c()

8.6 Scheduled functions

These functions are directly called by Basic Software Scheduler. The following func-
tions shall have no return value and no parameter. All functions shall be non reentrant.

8.6.1 Dcm_MainFunction

[SWS_Dcm_00053] d

260 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Dcm_MainFunction

Syntax void Dcm_MainFunction (
void
)

Service ID [hex] 0x25

Description This service is used for processing the tasks of the main loop.
Available via SchM_Dcm.h

c(SRS_BSW_00424, SRS_BSW_00373)

8.7 Expected interfaces

In this chapter all interfaces required from other modules are listed.

8.7.1 Mandatory interfaces

This section defines all interfaces, which are required to fulfill the core functionality of
the module.
[SWS_Dcm_91001] d
API Function Header File Description
ComM_DCM_ActiveDiagnostic ComM_Dcm.h Indication of active diagnostic by the DCM.
ComM_DCM_InactiveDiagnostic ComM_Dcm.h Indication of inactive diagnostic by the DCM.
PduR_DcmTransmit PduR_Dcm.h Requests transmission of a PDU.

c()

8.7.2 Optional interfaces

This section defines all interfaces, which are required to fulfill an optional functionality
of the module.
[SWS_Dcm_91002] d
API Function Header File Description
BndM_GetBlockPtr_<Block BndM_Externals.h –
Id.Shortname>
5

261 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
API Function Header File Description
BndM_WriteBlock_<Block BndM_Externals.h Will persist the data in flash, that it can later directly
Id.Shortname> accessed via BndM_GetBlockPtr API. The writing
take a while and is finished after the successful
callback xxx_BndMWriteBlockFinish
BndM_WriteCancel BndM.h Cancels the writing
BndM_WriteFinalize BndM.h Will trigger the finalization of writing phase. The
finish of asynchronous processing will trigger the
callback xxx_BndMWriteFinalizeFinish including the
result of this operation.
BndM_WriteStart BndM.h Will trigger the start of writing phase. The finish of
asynchronous processing will trigger the callback
xxx_BndMWriteStartFinish including the result of
this operation
BswM_Dcm_ApplicationUpdated BswM_Dcm.h This function is called by the DCM in order to report
an updated application.
BswM_Dcm_CommunicationMode BswM_Dcm.h Function called by DCM to inform the BswM about
_CurrentState the current state of the communication mode.
Dem_ClearDTC Dem.h Clears single DTCs, as well as groups of DTCs.
Dem_DcmGetAvailableOBDMIDs Dem_Dcm.h Reports the value of a requested
"availability-OBDMID" to the DCM upon a Service
$06 request. Derived from that the tester displays
the supported tests a mechanic can select from. API
is needed in OBD-relevant ECUs only.
API Availability: This API will be available only if
({ecuc(Dem/DemGeneral.DemOBDSupport)} !=
DEM_OBD_NO_OBD_SUPPORT)
Dem_DcmGetDTCOfOBDFreeze Dem_Dcm.h Gets DTC by freeze frame record number. API is
Frame needed in OBD-relevant ECUs only.
API Availability: This API will be available only if
({ecuc(Dem/DemGeneral.DemOBDSupport)} !=
DEM_OBD_NO_OBD_SUPPORT)
Dem_DcmGetDTRData Dem_Dcm.h Reports a DTR data along with TID-value, UaSID,
test result with lower and upper limit. API is needed
in OBD-relevant ECUs only.
API Availability: This API will be available only if
({ecuc(Dem/DemGeneral.DemOBDSupport)} !=
DEM_OBD_NO_OBD_SUPPORT)
Dem_DcmGetNumTIDsOfOBDMID Dem_Dcm.h Gets the number of TIDs per (functional) OBDMID.
This can be used by the DCM to iteratively request
for OBD/TID result data within a loop from
0....numberOfTIDs-1 API is needed in OBD-relevant
ECUs only.
API Availability: This API will be available only if
({ecuc(Dem/DemGeneral.DemOBDSupport)} !=
DEM_OBD_NO_OBD_SUPPORT)
Dem_DcmReadDataOfOBDFreeze Dem_Dcm.h Gets data element per PID and index of the most
Frame important freeze frame being selected for the output
of service $02. The function stores the data in the
provided DestBuffer. API is needed in OBD-relevant
ECUs only.
API Availability: This API will be available only if
({ecuc(Dem/DemGeneral.DemOBDSupport)} !=
DEM_OBD_NO_OBD_SUPPORT)
Dem_DisableDTCRecordUpdate Dem.h Disables the event memory update of a specific
DTC (only one at one time).
5

262 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
API Function Header File Description
Dem_DisableDTCSetting Dem.h Disables the DTC setting for all DTCs assigned to
the DemEventMemorySet of the addressed client.
Dem_EnableDTCRecordUpdate Dem.h Enables the event memory update of the DTC
disabled by Dem_DisableDTCRecordUpdate()
before.
Note: As the call to Dem_EnableDTCRecordUpdate
is the last action in the sequence of disabling/
enabling a DTC, the caller is not interested in the
return value. Therefore E_OK should be returned
even if the DTC is enabled asynchronously.
Dem_EnableDTCSetting Dem.h (Re)-Enables the DTC setting for all DTCs assigned
to the DemEventMemorySet of the addressed client.
Dem_GetDTCByOccurrenceTime Dem.h Gets the DTC by occurrence time. There is no
explicit parameter for the DTC-origin as the origin
always is DEM_DTC_ORIGIN_PRIMARY_
MEMORY.
Dem_GetDTCSeverityAvailabilityMask Dem.h Gets the DTC Severity availability mask.
Dem_GetDTCStatusAvailabilityMask Dem.h Gets the DTC Status availability mask of the
selected fault memory.
Dem_GetFunctionalUnitOfDTC Dem.h Gets the functional unit of the requested DTC.
Dem_GetNextExtendedDataRecord Dem.h Gets extended data record for the DTC selected by
Dem_SelectExtendedDataRecord. The function
stores the data in the provided DestBuffer.
Dem_GetNextFilteredDTC Dem.h Gets the next filtered DTC matching the filter
criteria. For UDS services, the interface has an
asynchronous behavior, because a large number of
DTCs has to be processed.
Dem_GetNextFilteredDTCAndFDC Dem.h Gets the next filtered DTC and its associated Fault
Detection Counter (FDC) matching the filter criteria.
The interface has an asynchronous behavior,
because a large number of DTCs has to be
processed and the FDC might be received
asynchronously from a SW-C, too.
Dem_GetNextFilteredDTCAndSeverity Dem.h Gets the next filtered DTC and its associated
Severity matching the filter criteria. The interface
has an asynchronous behavior, because a large
number of DTCs has to be processed.
Dem_GetNextFilteredRecord Dem.h Gets the next freeze frame record number and its
associated DTC stored in the event memory. The
interface has an asynchronous behavior, because
NvRAM access might be required.
Dem_GetNextFreezeFrameData Dem.h Gets freeze frame data by the DTC selected by
Dem_SelectFreezeFrameData. The function stores
the data in the provided DestBuffer.
Dem_GetNumberOfFilteredDTC Dem.h Gets the number of a filtered DTC.
Dem_GetNumberOfFreezeFrame Dem.h This function returns the number of all freeze frame
Records records currently stored in the primary event
memory
Dem_GetSeverityOfDTC Dem.h Gets the severity of the requested DTC. For large
configurations and DTC-calibration, the interface
behavior can be asynchronous (splitting the
DTC-search into segments).
Dem_GetSizeOfExtendedDataRecord Dem.h Gets the size of Extended Data Record by DTC
Selection selected by the call of Dem_SelectExtendedData
Record.
5

263 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
API Function Header File Description
Dem_GetSizeOfFreezeFrameSelection Dem.h Gets the size of freeze frame data by DTC selected
by the call of Dem_SelectFreezeFrameData.
Dem_GetStatusOfDTC Dem.h Gets the status of a DTC. For large configurations
and DTC-calibration, the interface behavior can be
asynchronous (splitting the DTC-search into
segments). The DTCs of OBD Events Suppression
shall be reported as Dem_WRONG_DTC.
Dem_GetTranslationType Dem.h Gets the supported DTC formats of the ECU.The
supported formats are configured via DemTypeOf
DTCSupported.
Dem_SetDTCFilter Dem.h Sets the DTC Filter.
The server shall perform a bit-wise logical AND-ing
operation between the parameter DTCStatusMask
and the current UDS status in the server. In addition
to the DTCStatusAvailabilityMask, the server shall
return all DTCs for which the result of the AND-ing
operation is non-zero [i.e. (statusOfDTC &
DTCStatusMask) != 0]. The server shall process
only the DTC Status bits that it is supporting. OBD
Events Suppression shall be ignored for this
computation. If no DTCs within the server match the
masking criteria specified in the clients request, no
DTC or status information shall be provided
following the DTCStatusAvailabilityMask byte in the
positive response message
(((statusOfDTC & DTCStatusMask) != 0) &&
((severity & DTCSeverityMask) != 0)) == TRUE
Dem_SetFreezeFrameRecordFilter Dem.h Sets a freeze frame record filter.
Det_ReportError Det.h Service to report development errors.
IdsM_SetSecurityEvent IdsM.h This API is the application interface to report
security events to the IdsM.
IdsM_SetSecurityEventWithContext IdsM.h This API is the application interface to report
Data security events with context data to the IdsM.
IoHwAb_Dcm_<EcuSignalName> IoHwAb_Dcm.h This function provides control access to a certain
ECU Signal to the DCM module (<EcuSignalname>
is the symbolic name of an ECU Signal). The ECU
signal can be locked and unlocked by this function.
Locking ’freezes’ the ECU signal to the current
value, the configured default value or a value given
by the parameter ’signal’.
IoHwAb_Dcm_Read<EcuSignal IoHwAb_Dcm.h This function provides read access to a certain ECU
Name> Signal to the DCM module (<EcuSignalname> is the
symbolic name of an ECU Signal).
NvM_ReadBlock NvM.h Service to copy the data of the NV block to its
corresponding RAM block.
NvM_SetBlockLockStatus NvM.h Service for setting the lock status of a permanent
RAM block or of the explicit synchronization of a
NVRAM block.
NvM_SetRamBlockStatus NvM.h Service for setting the RAM block status of a
permanent RAM block or the status of the explicit
synchronization of a NVRAM block.
NvM_WriteBlock NvM.h Service to copy the data of the RAM block to its
corresponding NV block.
PduR_DcmCancelReceive PduR_Dcm.h Requests cancellation of an ongoing reception of a
PDU in a lower layer transport protocol module.
5

264 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
API Function Header File Description
PduR_DcmCancelTransmit PduR_Dcm.h Requests cancellation of an ongoing transmission of
a PDU in a lower layer communication module.
SchM_ActMainFunction_Dcm <none> Invokes the SchM_ActMainFunction function to
trigger the activation of a corresponding main
processing function.

c()
Dem_DcmReadDataOfOBDFreezeFrame is only required when OBD Service $02 is
configured (see configuration parameter DcmDsdSidTabServiceId).

8.7.3 Configurable interfaces

This section defines the interfaces where the Dcm configuration defines the actual func-
tions that the Dcm will use. Depending on the configuration, an implementation of these
functions could be provided by other BSW-modules (typically the DEM) or by software-
components (through the RTE).

8.7.3.1 SecurityAccess

From the point of view of the DCM, the operation has the following signature:

8.7.3.1.1 GetSeed

If DcmDspSecurityADRSize is present:
[SWS_Dcm_01151] d
Service Name Xxx_GetSeed
Syntax Std_ReturnType Xxx_GetSeed (
const uint8* SecurityAccessDataRecord,
Dcm_OpStatusType OpStatus,
uint8* Seed,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x44

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) SecurityAccessData This data record contains additional data to calculate the seed
Record value; the size of this parameter is DcmDspSecurityADRSize
which is at least "1".
5

265 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) Seed Pointer for provided seed
ErrorCode If the operation Xxx_GetSeed returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description Request to application for asynchronous provision of seed value
Available via Dcm_Externals.h

c()
If DcmDspSecurityADRSize is not present:
[SWS_Dcm_91003] d
Service Name Xxx_GetSeed
Syntax Std_ReturnType Xxx_GetSeed (
Dcm_OpStatusType OpStatus,
uint8* Seed,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x45

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) Seed Pointer for provided seed
ErrorCode If the operation Xxx_GetSeed returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description Request to application for asynchronous provision of seed value
Available via Dcm_Externals.h

c()

8.7.3.1.2 CompareKey

[SWS_Dcm_91004] d

266 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Xxx_CompareKey

Syntax Std_ReturnType Xxx_CompareKey (
const uint8* Key,
Dcm_OpStatusType OpStatus,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x47

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) Key Key, which needs to be compared
OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) ErrorCode NRC to be sent if E_NOT_OK is returned
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
DCM_E_COMPARE_KEY_FAILED: Key did not match.
Description Request to application for asynchronous comparing key (DcmDspSecurityUsePort = USE_
ASYNCH_CLIENT_SERVER)
Available via Dcm_Externals.h

c()

8.7.3.1.3 GetSecurityAttemptCounter

[SWS_Dcm_01152] d
Service Name Xxx_GetSecurityAttemptCounter
Syntax Std_ReturnType Xxx_GetSecurityAttemptCounter (
Dcm_OpStatusType OpStatus,
uint8* AttemptCounter
)

Service ID [hex] 0x59

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL
Parameters (inout) None
Parameters (out) AttemptCounter The attempt counter for this security level
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description Read the attempt counter for a specific security level from the application
Available via Dcm_Externals.h

c()

267 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Note: In case the Security Access AttemptCounter needs to be shared between ap-
plication and bootloader, the application needs to consider this in the API-call Xxx_-
GetSecurityAttemptCounter (see chapter 7.6.4 Interaction). Further this has also
impact on the security delay timer which needs to be considered.

8.7.3.1.4 SetSecurityAttemptCounter

[SWS_Dcm_01153] d
Service Name Xxx_SetSecurityAttemptCounter
Syntax Std_ReturnType Xxx_SetSecurityAttemptCounter (
Dcm_OpStatusType OpStatus,
uint8 AttemptCounter
)

Service ID [hex] 0x5a

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL
AttemptCounter The attempt counter for this security level
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description Set the attempt counter for a specific security level in the application
Available via Dcm_Externals.h

c()

8.7.3.2 DataServices

From the point of view of the DCM, the operations have the following signatures:
Note : The OpStatus parameter shall only exist for asynchronous operations (if DcmD-
spDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or USE_DATA_-
ASYNCH_CLIENT_SERVER_ERROR or USE_DATA_ASYNCH_FNC or USE_DATA_-
ASYNCH_FNC_ERROR). In case of synchronous operations (DcmDspDataUsePort is
set to USE_DATA_SYNCH_CLIENT_SERVER or USE_DATA_SYNCH_FNC), the OpSta-
tus parameter shall not exist.

8.7.3.2.1 ReadData

If DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-

DATA_SYNCH_FNC, the following definition is used:

268 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

[SWS_Dcm_00793] d
Service Name Xxx_ReadData
Syntax Std_ReturnType Xxx_ReadData (
uint8* Data
)

Service ID [hex] 0x34

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) Data Buffer where the requested data shall be copied to
Return value Std_ReturnType E_OK: this value is always returned.
Description This function requests to the application a data value of a DID/PID if DcmDspDataUsePort is
set to USE_DATA_SYNCH_CLIENT_SERVER.
Available via Dcm_Externals.h

c()
If DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or
USE_DATA_ASYNCH_FNC, the following definition is used:
[SWS_Dcm_91006] d
Service Name Xxx_ReadData
Syntax Std_ReturnType Xxx_ReadData (
Dcm_OpStatusType OpStatus,
uint8* Data
)

Service ID [hex] 0x3b

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) Data Buffer where the requested data shall be copied to
Return value Std_ReturnType E_OK: Request was successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application a data value of a DID/PID if DcmDspDataUsePort is
set to USE_DATA_ASYNCH_CLIENT_SERVER.
Available via Dcm_Externals.h

c()
If DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER_ERROR or
USE_DATA_ASYNCH_FNC_ERROR, the following definition is used:
[SWS_Dcm_91005] d

269 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Xxx_ReadData

Syntax Std_ReturnType Xxx_ReadData (
Dcm_OpStatusType OpStatus,
uint8* Data,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x58

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) Data Buffer where the requested data shall be copied to
ErrorCode If the operation Xxx_ReadData returns value E_NOT_OK, the
Dcm module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application a data value of a DID/PID if DcmDspDataUsePort is
set to USE_DATA_ASYNCH_CLIENT_SERVER.
Available via Dcm_Externals.h

c()

8.7.3.2.2 WriteData

If DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-

DATA_SYNCH_FNC, the following definition is used:
If DcmDspDataType is NOT set to UINT8_DYN, the following definition is used:
[SWS_Dcm_00794] d
Service Name Xxx_WriteData
Syntax Std_ReturnType Xxx_WriteData (
const uint8* Data,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x51

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) Data Buffer containing the data to be written
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_WriteData returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
5

270 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests the application to write a data value of a DID.
Available via Dcm_Externals.h

c()
If DcmDspDataType is set to UINT8_DYN, the following definition is used:
[SWS_Dcm_91007] d
Service Name Xxx_WriteData
Syntax Std_ReturnType Xxx_WriteData (
const uint8* Data,
uint16 DataLength,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x52

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) Data Buffer containing the data to be written
DataLength Length in byte of the data to be written
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_WriteData returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests the application to write a data value of a DID.
Available via Dcm_Externals.h

c()
If DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or
USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR
USE_DATA_ASYNCH_FNC_ERROR, the following definition is used:
If DcmDspDataType is NOT set to UINT8_DYN, the following definition is used:
[SWS_Dcm_91008] d
Service Name Xxx_WriteData
Syntax Std_ReturnType Xxx_WriteData (
const uint8* Data,
Dcm_OpStatusType OpStatus,
Dcm_NegativeResponseCodeType* ErrorCode
)
5

271 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Service ID [hex] 0x35
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) Data Buffer containing the data to be written
OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_WriteData returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests the application to write a data value of a DID.
Available via Dcm_Externals.h

c()
If DcmDspDataType is set to UINT8_DYN, the following definition is used:
[SWS_Dcm_91009] d
Service Name Xxx_WriteData
Syntax Std_ReturnType Xxx_WriteData (
const uint8* Data,
uint16 DataLength,
Dcm_OpStatusType OpStatus,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x3e

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) Data Buffer containing the data to be written
DataLength Length in byte of the data to be written
OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_WriteData returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests the application to write a data value of a DID.
Available via Dcm_Externals.h

c()

272 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.7.3.2.3 ReadDataLength

If DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-

DATA_SYNCH_FNC, the following definition is used:
[SWS_Dcm_00796] d
Service Name Xxx_ReadDataLength
Syntax Std_ReturnType Xxx_ReadDataLength (
uint16* DataLength
)

Service ID [hex] 0x36

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) DataLength Length in byte of the data to be read
Return value Std_ReturnType E_OK: this value is always returned.
Description This function requests the application to return the data length in byte of a Data.
Available via Dcm_Externals.h

c()
If DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or USE_-
DATA_ASYNCH_CLIENT_SERVER_ERROR or USE_DATA_ASYNCH_FNC or USE_-
DATA_ASYNCH_FNC_ERROR, the following definition is used:
[SWS_Dcm_91010] d
Service Name Xxx_ReadDataLength
Syntax Std_ReturnType Xxx_ReadDataLength (
Dcm_OpStatusType OpStatus,
uint16* DataLength
)

Service ID [hex] 0x4c

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) DataLength Length in byte of the data to be read
Return value Std_ReturnType E_OK: this value is always returned.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests the application to return the data length in byte of a Data.
Available via Dcm_Externals.h

c()

273 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.7.3.2.4 ConditionCheckRead

If DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-

DATA_SYNCH_FNC, the following definition is used:
[SWS_Dcm_00797] d
Service Name Xxx_ConditionCheckRead
Syntax Std_ReturnType Xxx_ConditionCheckRead (
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x49

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ConditionCheckRead returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application if the conditions to read the Data are correct.
Available via Dcm_Externals.h

c()
If DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or
USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR
USE_DATA_ASYNCH_FNC_ERROR, the following definition is used:
[SWS_Dcm_91011] d
Service Name Xxx_ConditionCheckRead
Syntax Std_ReturnType Xxx_ConditionCheckRead (
Dcm_OpStatusType OpStatus,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x37

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ConditionCheckRead returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
5

274 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Description This function requests to the application if the conditions to read the Data are correct.
Available via Dcm_Externals.h

c()

8.7.3.2.5 GetScalingInformation

This function requests to the application for the scaling information of a Data (scaling-
Byte and scalingByteExtension).
If DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-
DATA_SYNCH_FNC, the following definition is used:
[SWS_Dcm_00798] d
Service Name Xxx_GetScalingInformation
Syntax Std_ReturnType Xxx_GetScalingInformation (
uint8* ScalingInfo,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x4b

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) ScalingInfo Scaling information (scalingByte and scalingByteExtension)
ErrorCode If the operation Xxx_GetScalingInformation returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application for the scaling information of a Data.
Available via Dcm_Externals.h

c()
If DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or
USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR
USE_DATA_ASYNCH_FNC_ERROR, the following definition is used:
[SWS_Dcm_91012] d

275 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Xxx_GetScalingInformation

Syntax Std_ReturnType Xxx_GetScalingInformation (
Dcm_OpStatusType OpStatus,
uint8* ScalingInfo,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x38

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) ScalingInfo Scaling information (scalingByte and scalingByteExtension)
ErrorCode If the operation Xxx_GetScalingInformation returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application for the scaling information of a Data.
Available via Dcm_Externals.h

c()

8.7.3.2.6 ReturnControlToECU

[SWS_Dcm_01285] d
Service Name Xxx_ReturnControlToECU
Syntax Std_ReturnType Xxx_ReturnControlToECU (
[Dcm_ControlMask_{DID}Type controlMask],
[uint8* controlMask2],
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x4f

Sync/Async Synchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)}== (USE_DATA_
SYNCH_FNC || USE_DATA_ASYNCH_FNC ||USE_DATA_ASYNCH_FNC_ERROR) &&
{ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidFreeze
CurrentState)} == TRUE) || ({ecuc(Dcm/Dc
controlMask –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == (USE_DATA_SYNCH_FNC || USE_DATA_
ASYNCH_FNC ||USE_DATA_ASYNCH_FNC_ERROR) &&
{ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDid
Control/DcmDspDidFreezeCurrentState)} == TRUE)||
5
5

276 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
4
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDid
Control/DcmDspDidResetToDefault)} == TRUE) || ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/
DcmDspDidShortTermAdjustment)}== TRUE) && ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} ==
DCM_CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/
DcmDspDidControl/DcmDspDidControlMaskSize)} <= 0x04)
controlMask2 –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == (USE_DATA_SYNCH_FNC || USE_DATA_
ASYNCH_FNC ||USE_DATA_ASYNCH_FNC_ERROR) &&
{ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDid
Control/DcmDspDidFreezeCurrentState)} == TRUE)||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDid
Control/DcmDspDidResetToDefault)} == TRUE) || ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/
DcmDspDidShortTermAdjustment)}== TRUE) && ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} ==
DCM_CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspDid/?DcmDspDidInfoRef->DcmDspDidInfo/
DcmDspDidControl/DcmDspDidControlMaskSize)} => 0x05)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ReturnControlToECU returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application to return control to ECU of an IOControl.
Available via Dcm_Externals.h

c()
Note: Square brackets [] indicate that an argument is optional.

8.7.3.2.7 ResetToDefault

8.7.3.2.7.1 Synchronous interface

[SWS_Dcm_01286] d
Service Name Xxx_ResetToDefault
Syntax Std_ReturnType Xxx_ResetToDefault (
[Dcm_ControlMask_{DID}Type controlMask],
[uint8* controlMask2],
Dcm_NegativeResponseCodeType* ErrorCode
)
5

277 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Service ID [hex] 0x4d
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) controlMask –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == (USE_DATA_SYNCH_FNC)) && ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDsp
DidResetToDefault)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDspDidInfo/Dcm
DspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/?DcmConfigSet/
DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/Dcm
DspDidControl/DcmDspDidControlMaskSize)} <= 0x04)
controlMask2 –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == (USE_DATA_SYNCH_FNC)) && ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDsp
DidResetToDefault)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspDid/DcmDspDidInfoRef -> DcmDspDidInfo/
DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/Dcm
DspDidControl/DcmDspDidControlMaskSize)} => 0x05)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ResetToDefault returns value E_NOT_OK,
the DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application to reset an IOControl to default value.
Available via Dcm_Externals.h

c()
Note: Square brackets [] indicate that an argument is optional.

8.7.3.2.7.2 Asynchronous interface

[SWS_Dcm_01314] d
Service Name Xxx_ResetToDefault
Syntax Std_ReturnType Xxx_ResetToDefault (
Dcm_OpStatusType OpStatus,
[Dcm_ControlMask_{DID}Type controlMask],
[uint8* controlMask2],
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x3c

Sync/Async Asynchronous
5

278 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
controlMask –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == (USE_DATA_ASYNCH_FNC || USE_DATA_
ASYNCH_FNC_ERROR))&& ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidResetTo
Default)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDid/DcmDspDidInfoRef -> DcmDspDidInfo/DcmDspDid
Control/DcmDspDidControlMask)} == DCM_CONTROLMASK_
EXTERNAL)&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Did/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/
DcmDspDidControlMaskSize)} <= 0x04)
controlMask2 –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == (USE_DATA_ASYNCH_FNC || USE_DATA_
ASYNCH_FNC_ERROR))&& ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidResetTo
Default)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDid/DcmDspDidInfoRef -> DcmDspDidInfo/DcmDspDid
Control/DcmDspDidControlMask)} == DCM_CONTROLMASK_
EXTERNAL)&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Did/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/
DcmDspDidControlMaskSize)} => 0x05)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ResetToDefault returns value E_NOT_OK,
the DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application to reset an IOControl to default value.
Available via Dcm_Externals.h

c()
Note: Square brackets [] indicate that an argument is optional.

8.7.3.2.8 FreezeCurrentState

8.7.3.2.8.1 Synchronous interface

[SWS_Dcm_01290] d
Service Name Xxx_FreezeCurrentState
5

279 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Syntax Std_ReturnType Xxx_FreezeCurrentState (
[Dcm_ControlMask_{DID}Type controlMask],
[uint8* controlMask2],
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x4a

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) controlMask –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == USE_DATA_SYNCH_FNC)&& ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDsp
DidFreezeCurrentState)} == TRUE) && ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspDid/DcmDspDidInfoRef -> DcmDspDidInfo/
DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/Dcm
DspDidControl/DcmDspDidControlMaskSize)} <= 0x04)
controlMask2 –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == USE_DATA_SYNCH_FNC)&& ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDsp
DidFreezeCurrentState)} == TRUE) && ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspDid/DcmDspDidInfoRef -> DcmDspDidInfo/
DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/Dcm
DspDidControl/DcmDspDidControlMaskSize)} => 0x05)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_FreezeCurrentState returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application to freeze the current state of an IOControl.
Available via Dcm_Externals.h

c()
Note: Square brackets [] indicate that an argument is optional.

8.7.3.2.8.2 Asynchronous interface

[SWS_Dcm_01315] d
Service Name Xxx_FreezeCurrentState
5

280 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Syntax Std_ReturnType Xxx_FreezeCurrentState (
Dcm_OpStatusType OpStatus,
[Dcm_ControlMask_{DID}Type controlMask],
[uint8* controlMask2],
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex]
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
controlMask –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == (USE_DATA_ASYNCH_FNC || USE_DATA_
ASYNCH_FNC_ERROR))&& ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidFreeze
CurrentState)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDid/DcmDspDidInfoRef -> DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/Dcm
DspDidControl/DcmDspDidControlMaskSize)} <= 0x04)
controlMask2 –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == (USE_DATA_ASYNCH_FNC || USE_DATA_
ASYNCH_FNC_ERROR))&& ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidFreeze
CurrentState)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDid/DcmDspDidInfoRef -> DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/Dcm
DspDidControl/DcmDspDidControlMaskSize)} => 0x05)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_FreezeCurrentState returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application to freeze the current state of an IOControl.
Available via Dcm_Externals.h

c()

8.7.3.2.9 ShortTermAdjustment

8.7.3.2.9.1 Synchronous interface

[SWS_Dcm_00802] d

281 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Xxx_ShortTermAdjustment

Syntax Std_ReturnType Xxx_ShortTermAdjustment (
const uint8* ControlStateInfo,
[Dcm_ControlMask_{DID}Type controlMask],
[uint8* controlMask2],
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x50

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) ControlStateInfo ControlState information contained in the ControlOptionRecord
parameter of the InputOutputControlByIdentifier diagnostic
request
controlMask –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == USE_DATA_SYNCH_FNC) && ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDsp
DidShortTermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspData.DcmDspDataType} != UINT8_DYN)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef -> DcmDspDidInfo/DcmDspDidControl/DcmDspDid
ControlMask)} == DCM_CONTROLMASK_EXTERNAL)&&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
MaskSize)} <= 0x04)
controlMask2 –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == USE_DATA_SYNCH_FNC) && ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDsp
DidShortTermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspData.DcmDspDataType} != UINT8_DYN)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef -> DcmDspDidInfo/DcmDspDidControl/DcmDspDid
ControlMask)} == DCM_CONTROLMASK_EXTERNAL)&&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
MaskSize)} >= 0x05)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ShortTermAdjustment returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application to adjust the IO signal.
Available via Dcm_Externals.h

c()
Note: Square brackets [] indicate that an argument is optional.

8.7.3.2.9.2 Asynchronous interface

[SWS_Dcm_01316] d

282 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Xxx_ShortTermAdjustment

Syntax Std_ReturnType Xxx_ShortTermAdjustment (
const uint8* ControlStateInfo,
uint16 DataLength,
Dcm_OpStatusType OpStatus,
[Dcm_ControlMask_{DID}Type controlMask],
[uint8* controlMask2],
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x55

Sync/Async Asynchronous
Reentrancy Non Reentrant

Parameters (in) ControlStateInfo ControlState information contained in the ControlOptionRecord

parameter of the InputOutputControlByIdentifier diagnostic
request
DataLength Length in byte of the data to be written
OpStatus Status of the current operation
controlMask –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == (USE_DATA_ASYNCH_FNC || USE_DATA_
ASYNCH_FNC_ERROR))&& ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShortTerm
Adjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspData.DcmDspDataType} == UINT8_DYN) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref -> DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)}
<= 0x04)
controlMask2 –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == (USE_DATA_ASYNCH_FNC || USE_DATA_
ASYNCH_FNC_ERROR))&& ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShortTerm
Adjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspData.DcmDspDataType} == UINT8_DYN) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref -> DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)}
>= 0x05)
Parameters (inout) None
Parameters (out) ErrorCode NRC to be sent in the negative response in case of failure (E_
NOT_OK)
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application to adjust the IO signal.
Available via Dcm_Externals.h

c()

283 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.7.3.3 DataServices_DIDRange

From the point of view of the DCM, the operations have the following signatures:
Note : The OpStatus parameter should only be used for asynchronous operations
(if DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or USE_-
DATA_ASYNCH_FNC or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR USE_DATA_-
ASYNCH_FNC_ERROR). In case of synchronous operations (DcmDspDataUsePort is
set to USE_DATA_SYNCH_CLIENT_SERVER or USE_DATA_SYNCH_FNC), the OpSta-
tus parameter should not be used.

8.7.3.3.1 IsDidAvailable

[SWS_Dcm_00803] d
Service Name Xxx_IsDidAvailable
Syntax Std_ReturnType Xxx_IsDidAvailable (
uint16 DID,
Dcm_OpStatusType OpStatus,
Dcm_DidSupportedType* supported
)

Service ID [hex] 0x53

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) DID DID value
OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) supported Indicate if the DID is available within the range. Returning DCM_
DID_SUPPORTED means it is supported within the range,
Returning DCM_DID_NOT_SUPPORTED means it is not
supported within the range
Return value Std_ReturnType E_OK: This value is returned when the Did is finally available.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests if a specific DID is available within the range or not.
Available via Dcm_Externals.h

c()

8.7.3.3.2 ReadDidData

[SWS_Dcm_00804] d

284 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Xxx_ReadDidData

Syntax Std_ReturnType Xxx_ReadDidData (
uint16 DID,
uint8* Data,
Dcm_OpStatusType OpStatus,
uint16 DataLength,
Dcm_NegativeResponseCodeType ErrorCode
)

Service ID [hex] 0x40

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) DID Data ID value
OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) Data Buffer where the requested data shall be copied to
DataLength Length of the data to be read
ErrorCode If the operation Xxx_ReadDidData returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application a data value of a DID
Available via Dcm_Externals.h

c()

8.7.3.3.3 WriteDidData

[SWS_Dcm_00805] d
Service Name Xxx_WriteDidData
Syntax Std_ReturnType Xxx_WriteDidData (
uint16 DID,
const uint8* Data,
Dcm_OpStatusType OpStatus,
uint16 DataLength,
Dcm_NegativeResponseCodeType ErrorCode
)

Service ID [hex] 0x41

Sync/Async Asynchronous
Reentrancy Non Reentrant
DID Data ID value
Data Buffer containing the data to be written
OpStatus Status of the current operation
5

285 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
DataLength Length of the data to be written
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_WriteDidData returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests the application to write a data value of a DID.
Available via Dcm_Externals.h

c()

8.7.3.3.4 ReadDidRangeDataLength

ReadDidRangeDataLength requests the application to return the data length of a DID

range. This interface is used for UDS Service ReadDataByIdentifier.
[SWS_Dcm_01271] d
Service Name Xxx_ReadDidRangeDataLength
Syntax Std_ReturnType Xxx_ReadDidRangeDataLength (
uint16 DID,
Dcm_OpStatusType OpStatus,
uint16* DataLength
)

Service ID [hex] 0x5e

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) DID Data ID value
OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) DataLength Length of the data to be written/read
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests the application to return the data length of a DID Range.
Available via Dcm_Externals.h

c()

286 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.7.3.4 InfoTypesServices

8.7.3.4.1 GetInfotypeValueData

[SWS_Dcm_91014] d
Service Name Xxx_GetInfotypeValueData
Syntax Std_ReturnType Xxx_GetInfotypeValueData (
Dcm_OpStatusType OpStatus,
uint8* DataValueBuffer,
uint8* DataValueBufferSize
)

Service ID [hex] 0x60

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) DataValueBufferSize When the function is called this parameter contains the maximum
number of data bytes that can be written to the buffer. The callee
fills in the number of written data bytes in DataValueBuffer.
Parameters (out) DataValueBuffer Buffer containing the Infotype information
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description The function provides the data related to the requested Infotype.
Available via Dcm_Externals.h

c()

8.7.3.5 RoutineServices

The operations mentioned in the following sub-chapters are only general examples,
because the number of In and OUT parameters can be variable from 0 to an arbitrary
number.It is therefore not possible to list all variations of operation prototypes.

8.7.3.5.1 Xxx_Start Operation

[SWS_Dcm_01203] d
Service Name Xxx_Start
Syntax Std_ReturnType Xxx_Start (
[DcmDspRoutineSignalType dataIn_1, ...
DcmDspRoutineSignalType dataIn_n],
[const uint8* dataInVar],
5
5

287 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
4
Dcm_OpStatusType OpStatus,
[DcmDspRoutineSignalType dataOut_1, ...
DcmDspRoutineSignalType dataOut_n],
[uint8* dataOutVar],
[uint16* currentDataLength],
Dcm_NegativeResponseCodeType ErrorCode
)

Service ID [hex] 0x5b

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) dataIn_1 Fixed-length input data provided in the routine control request
... ...
dataIn_n Fixed-length input data provided in the routine control request
dataInVar Variable-length input data provided in the routine control request
OpStatus Status of the current operation
Parameters (inout) currentDataLength If variable length routine input data is used, this parameter
contains the length in bytes of the dataInVar array. If variable
length routine output data is used, this parameter contains the
length in bytes of the dataOutVar parameter.

Parameters (out) dataOut_1 Fixed-length output data to provide in the routine control response
... ...
dataOut_n Fixed-length output data to provide in the routine control response
dataOutVar Variable-length output data to provide in the routine control
response
ErrorCode If the operation Xxx_Start returns value E_NOT_OK, the Dcm
module shall send a negative response with NRC code equal to
the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
DCM_E_FORCE_RCRRP: application requests the transmission
of a response Pending (NRC 0x78)
Description This function requests to the application to start the execution of a routine.
Available via Dcm_Externals.h

c()
Note: Square brackets [] indicate that an argument is optional.

8.7.3.5.2 Xxx_StartConfirmation Operation

[SWS_Dcm_91016] d

288 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Xxx_StartConfirmation

Syntax Std_ReturnType Xxx_StartConfirmation (
Dcm_ConfirmationStatusType ConfirmationStatus
)

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) ConfirmationStatus Confirmation status of a StartRoutine request
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function indicates the transmission of a response to a StartRoutine request
Available via Dcm_Externals.h

c()
Note: Square brackets [] indicate that an argument is optional.

8.7.3.5.3 Xxx_Stop Operation

[SWS_Dcm_01204] d
Service Name Xxx_Stop
Syntax Std_ReturnType Xxx_Stop (
[DcmDspRoutineSignalType dataIn_1, ...
DcmDspRoutineSignalType dataIn_n],
[const uint8* dataInVar],
[DcmDspRoutineSignalType dataOut_1, ...
DcmDspRoutineSignalType dataOut_n],
[uint8* dataOutVar],
[uint16* currentDataLength],
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x5c

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) dataIn_1 Fixed-length input data provided in the routine control request
... ...
dataIn_n Fixed-length input data provided in the routine control request
dataInVar Variable-length input data provided in the routine control request
Parameters (inout) currentDataLength If variable length routine input data is used, this parameter
contains the length in bytes of the dataInVar array. If variable
length routine output data is used, this parameter contains the
length in bytes of the dataOutVar parameter.
dataOut_1 Fixed-length output data to provide in the routine control response
... ...
5

289 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
dataOut_n Fixed-length output data to provide in the routine control response
dataOutVar Variable-length output data to provide in the routine control
response
ErrorCode If the operation Xxx_Stop returns value E_NOT_OK, the Dcm
module shall send a negative response with NRC code equal to
the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish
DCM_E_FORCE_RCRRP: application requests the transmission
of a response Pending (NRC 0x78)
Description This function requests to the application to stop the execution of a routine
Available via Dcm_Externals.h

c()
Note: Square brackets [] indicate that an argument is optional.

8.7.3.5.4 Xxx_StopConfirmation Operation

[SWS_Dcm_91017] d
Service Name Xxx_StopConfirmation
Syntax Std_ReturnType Xxx_StopConfirmation (
Dcm_ConfirmationStatusType ConfirmationStatus
)

Service ID [hex] 0x69

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) ConfirmationStatus Dcm_ConfirmationStatus Confirmation status of a StopRoutine
request
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function indicates the transmission of a response to a StopRoutine request
Available via Dcm_Externals.h

c()
Note: Square brackets [] indicate that an argument is optional.

8.7.3.5.5 Xxx_RequestResults Operation

[SWS_Dcm_91013] d

290 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Xxx_RequestResults

Syntax Std_ReturnType Xxx_RequestResults (
Dcm_OpStatusType OpStatus,
[DcmDspRoutineSignalType* dataIn_1, ...
DcmDspRoutineSignalType* dataIn_n],
[const uint8* dataInVar],
[DcmDspRoutineSignalType* dataOut_1, ...
DcmDspRoutineSignalType* dataOut_n],
[uint8* dataOutVar],
[uint16* variableDataLength],
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x71

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
dataIn_1 Fixed-length input data provided in the routine control request
... ...
dataIn_n Fixed-length input data provided in the routine control request
dataInVar Variable-length input data provided in the routine control request
Parameters (inout) variableDataLength Length in bytes of the dataOutVar parameter.

Parameters (out) dataOut_1 Fixed-length Output data to provide in the routine control
response
... ...
dataOut_n Fixed-length Output data to provide in the routine control
response
dataOutVar Variable-length Output data to provide in the routine control
response
ErrorCode If the operation Xxx_RequestResults returns value E_NOT_OK,
the Dcm module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish
DCM_E_FORCE_RCRRP: application requests the transmission
of a response Pending (NRC 0x78)
Description This function requests to the application the result of a routine execution
Available via Dcm_Externals.h

c()
Note: Square brackets [] indicate that an argument is optional.

8.7.3.5.6 Xxx_RequestResultsConfirmation Operation

[SWS_Dcm_91018] d

291 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Xxx_RequestResultsConfirmation

Syntax Std_ReturnType Xxx_RequestResultsConfirmation (
Dcm_ConfirmationStatusType ConfirmationStatus
)

Service ID [hex] 0x70

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) ConfirmationStatus Confirmation status of a RequestRoutineResults request
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function indicates the transmission of a response to a RequestRoutineResults request
Available via Dcm_Externals.h

c()
Note: Square brackets [] indicate that an argument is optional.

8.7.3.6 RequestControlServices

From the point of view of the DCM, the operation has the following signature:

8.7.3.6.1 RequestControl callout

[SWS_Dcm_01338] d
Service Name Xxx_RequestControl
Syntax Std_ReturnType Xxx_RequestControl (
uint8* OutBuffer,
const uint8* InBuffer
)

Service ID [hex] 0x63

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) None
Parameters (inout) OutBuffer Output buffer in which the RequestControl function can store its
result
InBuffer Input buffer containing the data of the OBD Service 0x08 request
Parameters (out) None
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
5

292 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Description Invokes a TID-specific function taking a configured number of bytes as input and returing a
fixed number of bytes as output. This is typically used to implement OBD Service $08
Available via Dcm_Externals.h

c()

8.7.3.7 CallbackDCMRequestServices

From the point of view of the DCM, the operations have the following signatures:

8.7.3.7.1 StartProtocol

[SWS_Dcm_01339] d
Service Name Xxx_StartProtocol
Syntax Std_ReturnType Xxx_StartProtocol (
Dcm_ProtocolType ProtocolType,
uint16 TesterSourceAddress,
uint16 ConnectionId
)

Service ID [hex] 0x67

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) ProtocolType Type of the protocol to be started
TesterSourceAddress source address of the tester
ConnectionId Unique connection identifier
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
E_PROTOCOL_NOT_ALLOWED: Protocol not allowed
Description This function allows the application to examine the environment conditions and enable/disable
further processing of the protocol.
Available via Dcm_Externals.h

c()

8.7.3.7.2 StopProtocol

[SWS_Dcm_01340] d

293 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Xxx_StopProtocol

Syntax Std_ReturnType Xxx_StopProtocol (
Dcm_ProtocolType ProtocolType,
uint16 TesterSourceAddress,
uint16 ConnectionId
)

Service ID [hex] 0x64

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) ProtocolType Type of the protocol to be stopped
TesterSourceAddress source address of the tester
ConnectionId Unique connection identifier
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function informs the application of the protocol stop.
Available via Dcm_Externals.h

c()

8.7.3.8 ServiceRequestNotification

From the point of view of the DCM, the operations has the following signatures:

8.7.3.8.1 Indication

[SWS_Dcm_01341] d
Service Name Xxx_Indication
Syntax Std_ReturnType Xxx_Indication (
uint8 SID,
const uint8* RequestData,
uint32 DataSize,
uint8 ReqType,
uint16 ConnectionId,
Dcm_NegativeResponseCodeType* ErrorCode,
Dcm_ProtocolType ProtocolType,
uint16 TesterSourceAddress
)

Service ID [hex] 0x65

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) SID –
5

294 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
RequestData Complete request data (diagnostic buffer), except the service ID
DataSize Number of valid bytes in the RequestData parameter
ReqType Addressing type of the request(0=physical request,1=functional
request)
ConnectionId Unique connection identifier
ProtocolType Type of the protocol to be indicated
TesterSourceAddress source address of the tester
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_Indication re- turns value E_NOT_OK, the
Dcm module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
E_REQUEST_NOT_ACCEPTED : Request not accepted
Description This function indicates to the application that a service is about to be executed and allows the
application to reject the execution of the service request
Available via Dcm_Externals.h

c()

8.7.3.8.2 Confirmation

[SWS_Dcm_01342] d
Service Name Xxx_Confirmation
Syntax Std_ReturnType Xxx_Confirmation (
uint8 SID,
uint8 ReqType,
uint16 ConnectionId,
Dcm_ConfirmationStatusType ConfirmationStatus,
Dcm_ProtocolType ProtocolType,
uint16 TesterSourceAddress
)

Service ID [hex] 0x66

Sync/Async Synchronous
Reentrancy Non Reentrant

Parameters (in) SID Value of service identifier

ReqType Addressing type of the request(0=physical request,1=functional
request)
ConnectionId Unique connection identifier
ConfirmationStatus Confirmation of a successful transmission or a transmission error
of a diagnostic service.
ProtocolType Type of Dcm Protocol
TesterSourceAddress source address of the tester
Parameters (inout) None
Parameters (out) None
5

295 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function confirms to the application the successful transmission or a transmission error of
a diagnostic service.
Available via Dcm_Externals.h

c()

8.7.3.9 ClearDTCCheckFnc

From the point of view of the Dcm, the operation has the following signature:
[SWS_Dcm_01270] d
Service Name Xxx_ClearDTCCheckFnc
Syntax Std_ReturnType Xxx_ClearDTCCheckFnc (
uint32 GoDTC,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x5f

Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) GoDTC requested groupOfDTC
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ClearDTCCheckFnc returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: application allows to clear the requested groupOfDTC
E_NOT_OK: application does not allow to clear the requested
groupOfDTC. Dcm shall send a negative response with the NRC
returned in the ErrorCode
Description Callout function for condition check, manufacturer / supplier specific checks on the groupOf
DTC, which is requested to clear.
Available via Dcm_Externals.h

c()

8.7.3.10 UploadDownloadServices

From the point of view of the DCM, the operations has the following signatures:

8.7.3.10.1 ProcessRequestDownload

[SWS_Dcm_00754] d

296 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Service Name Xxx_ProcessRequestDownload

Syntax Std_ReturnType Xxx_ProcessRequestDownload (
Dcm_OpStatusType OpStatus,
uint8 DataFormatIdentifier,
uint8 MemoryIdentifier,
uint32 MemoryAddress,
uint32 MemorySize,
uint32* BlockLength,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x30

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL
DataFormatIdentifier Bit 7 - 4: Compression Method
• 0x0: not compressed
• 0x1..F: vehicle-manufacturer-specific
Bit 3 - 0: Encrypting method
• 0x0: not encrypted
• 0x1..F: vehicle-manufacturer-specific
MemoryIdentifier Identifier of the Memory Block, if the parameter is not used it shall
be set to 0.
MemoryAddress Starting address of server memory to which data is to be written
MemorySize Uncompressed memory size in bytes
Parameters (inout) BlockLength Max. Number of bytes for one Dcm_WriteMemory
Parameters (out) ErrorCode If the operation Dcm_ProcessRequestDownload returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
Description Callout function. DCM shall call this callout function to start a download process. This service is
needed for the implementation of UDS service RequestDownload.
Available via Dcm_Externals.h

c()

8.7.3.10.2 ProcessRequestTransferExit

[SWS_Dcm_00755] d
Service Name Xxx_ProcessRequestTransferExit
Syntax Std_ReturnType Xxx_ProcessRequestTransferExit (
Dcm_OpStatusType OpStatus,
Dcm_NegativeResponseCodeType* ErrorCode
)
5

297 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Service ID [hex] 0x32
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL
Parameters (inout) None
Parameters (out) ErrorCode see below
Return value Std_ReturnType E_OK: Transfer was successful
E_NOT_OK: Transfer was not successful or the response buffer
is too small
DCM_E_PENDING: Transfer is not yet finished
Description Callout function. DCM shall call this callout function to terminate a download or upload process.
This callout is needed for the implementation of UDS service RequestTransferExit.
Available via Dcm_Externals.h

c()

8.7.3.10.3 ProcessRequestUpload

[SWS_Dcm_00756] d
Service Name Xxx_ProcessRequestUpload
Syntax Std_ReturnType Xxx_ProcessRequestUpload (
Dcm_OpStatusType OpStatus,
uint8 DataFormatIdentifier,
uint8 MemoryIdentifier,
uint32 MemoryAddress,
uint32 MemorySize,
uint32* BlockLength,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x31

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_FORCE_
RCRRP_OK
DataFormatIdentifier Bit 7 - 4: Compression Method
• 0x0: not compressed
• 0x1..F: vehicle-manufacturer-specific
Bit 3 - 0: Encrypting method
• 0x0: not encrypted
• 0x1..F: vehicle-manufacturer-specific
MemoryIdentifier Identifier of the Memory Block, if the parameter is not used it shall
be set to 0.
MemoryAddress Starting address of server memory from which data are to be
copied
MemorySize Uncompressed memory size in bytes
5

298 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Parameters (inout) BlockLength Max. Number of bytes for one Dcm_ReadMemory
Parameters (out) ErrorCode If the operation Dcm_ProcessRequestUpload returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
Description Callout function. DCM shall call this callout function to start an upload process. This service is
needed for the implementation of UDS service RequestUpload.
Available via Dcm_Externals.h

c()

8.7.3.10.4 ProcessTransferDataRead

[SWS_Dcm_91070] d
Service Name Xxx_ProcessTransferDataRead
Syntax Dcm_ReturnReadMemoryType Xxx_ProcessTransferDataRead (
Dcm_OpStatusType OpStatus,
uint8 MemoryIdentifier,
uint32 MemoryAddress,
uint32 MemorySize,
Dcm_RequestDataArrayType MemoryData,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x26

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_FORCE_
RCRRP_OK
MemoryIdentifier Identifier of the Memory Block (e.g. used if memory section
distinguishing is needed) Note: If it’s not used this parameter
shall be set to 0.
MemoryAddress Starting address of server memory from which data is to be
retrieved.
MemorySize Number of bytes in the MemoryData
Parameters (inout) None
Parameters (out) MemoryData Data read (Points to the diagnostic buffer in DCM)
ErrorCode If the operation Dcm_ReadMemory returns value DCM_READ_
FAILED, the Dcm module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Dcm_ReturnRead DCM_READ_OK: read was successful
MemoryType DCM_READ_FAILED: read was not successful
DCM_READ_PENDING: read is not yet finished
DCM_READ_FORCE_RCRRP: reading is pending, the
Response pending transmission starts immediately
5

299 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Description The ProcessTransferDataRead callout is used to request memory data identified by the
parameter memoryAddress and memorySize from the UDS request message. This service is
needed for the implementation of UDS services:
• ReadMemoryByAddress
• RequestUpload
• ReadDataByIdentifier (in case of Dynamical DID defined by memory address)
• TransferData
Available via Dcm_Externals.h

c()

8.7.3.10.5 ProcessTransferDataWrite

[SWS_Dcm_91071] d
Service Name Xxx_ProcessTransferDataWrite
Syntax Dcm_ReturnWriteMemoryType Xxx_ProcessTransferDataWrite (
Dcm_OpStatusType OpStatus,
uint8 MemoryIdentifier,
uint32 MemoryAddress,
uint32 MemorySize,
const Dcm_RequestDataArrayType MemoryData,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x27

Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_FORCE_
RCRRP_OK
MemoryIdentifier Identifier of the Memory Block (e.g. used by WriteDataByIdentifier
service). Note: If it’s not used this parameter shall be set to 0.
MemoryAddress Starting address of server memory in which data is to be copied.
Note: If it’s not used (e.g. if the data is compressed) this
parameter shall be set to 0.
MemorySize Number of bytes in MemoryData
MemoryData Data to write (Points to the diagnostic buffer in DCM)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Dcm_WriteMemory returns value DCM_WRITE_
FAILED, the Dcm module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Dcm_ReturnWrite DCM_WRITE_OK: write was successful
MemoryType DCM_WRITE_FAILED: write was not successful
DCM_WRITE_PENDING: write is not yet finished
DCM_WRITE_FORCE_RCRRP: writing is pending, the
Response pending transmission starts immediately
5

300 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Description The ProcessTransferDataWrite callout is used to write memory data identified by the parameter
memoryAddress and memorySize. This service is needed for the implementation of UDS
services :
• WriteMemoryByAddress
• RequestDownload
• TransferData
Available via Dcm_Externals.h

c()

8.8 Dcm as Service-Component

8.8.1 Implementation Data Types

8.8.1.1 Dcm_OpStatusType

[SWS_Dcm_00984] d
Name Dcm_OpStatusType
Kind Type
Derived from uint8
Range DCM_INITIAL 0x00 Indicates the initial call to the
operation
DCM_PENDING 0x01 Indicates that a pending return
has been done on the previous
call of the operation
DCM_CANCEL 0x02 Indicates that the DCM requests
to cancel the pending operation
DCM_FORCE_RCRRP_OK 0x03 Confirm a response pending
transmission
Description –
Variation –
Available via Rte_Dcm_Type.h

c()

8.8.1.2 Dcm_ConfirmationStatusType

[SWS_Dcm_00983] d

301 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name Dcm_ConfirmationStatusType
Kind Type
Derived from uint8
Range DCM_RES_POS_OK 0x00 –
DCM_RES_POS_NOT_OK 0x01 –
DCM_RES_NEG_OK 0x02 –
DCM_RES_NEG_NOT_OK 0x03 –
Description –
Variation –
Available via Rte_Dcm_Type.h

c()

8.8.1.3 Dcm_SecLevelType

[SWS_Dcm_00977] d
Name Dcm_SecLevelType
Kind Type
Derived from uint8
Range DCM_SEC_LEV_LOCKED 0x00 –
configuration dependent 0x01...0x3F –
Reserved by Document 0x40...0xFF –
Description Security Level type definition
Variation –
Available via Rte_Dcm_Type.h

c()

8.8.1.4 Dcm_SesCtrlType

[SWS_Dcm_00978] d
Name Dcm_SesCtrlType
Kind Type
Derived from uint8
DCM_DEFAULT_SESSION 0x01 –
DCM_PROGRAMMING_ 0x02 –
SESSION
DCM_EXTENDED_ 0x03 –
DIAGNOSTIC_SESSION
5

302 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
DCM_SAFETY_SYSTEM_ 0x04 –
DIAGNOSTIC_SESSION
configuration dependent 0x40...0x7E (according to "diagnosticSession
Type" parameter of Diagnostic
SessionControl request)
Description Session type definition. 0, 127 and all values above 127 are reserved by ISO.
Variation –
Available via Rte_Dcm_Type.h

c()

8.8.1.5 Dcm_ProtocolType

[SWS_Dcm_00979] d
Name Dcm_ProtocolType
Kind Type
Derived from uint8
DCM_OBD_ON_CAN 0x00 OBD on CAN (ISO15765-4;
ISO15031-5)
DCM_OBD_ON_FLEXRAY 0x01 (OBD on Flexray (Manufacturer
specific; ISO15031-5))
DCM_OBD_ON_IP 0x02 (OBD on Internet Protocol
(Manufacturer specific;
ISO15031-5))
DCM_UDS_ON_CAN 0x03 UDS on CAN (ISO15765-3;
ISO14229-1)
DCM_UDS_ON_FLEXRAY 0x04 UDS on FlexRay (Manufacturer
specific; ISO14229-1)
DCM_UDS_ON_IP 0x05 (UDS on Internet Protocol
(Manufacturer specific;
ISO14229-1))
DCM_ROE_ON_CAN 0x06 Response On Event on CAN
DCM_ROE_ON_FLEXRAY 0x07 Response On Event on FlexRay
DCM_ROE_ON_IP 0x08 (Response on Event on Internet
Protocol)
DCM_PERIODICTRANS_ON_ 0x09 Periodic Transmission on CAN
CAN
DCM_PERIODICTRANS_ON_ 0x0A Periodic Transmission on FlexRay
FLEXRAY
DCM_PERIODICTRANS_ON_IP 0x0B (Periodic Transmission on Internet
Protocol)
DCM_NO_ACTIVE_PROTOCOL 0x0C No protocol has been started
DCM_UDS_ON_LIN 0x0D UDS on LIN (ISO14229-1;
ISO14229-7)
Reserved for further AUTOSAR 0x0E..0xEF –
implementation
5

303 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
DCM_SUPPLIER_1 0xF0 Reserved for SW supplier
specific.
DCM_SUPPLIER_2 0xF1 Reserved for SW supplier
specific.
DCM_SUPPLIER_3 0xF2 Reserved for SW supplier
specific.
DCM_SUPPLIER_4 0xF3 Reserved for SW supplier
specific.
DCM_SUPPLIER_5 0xF4 Reserved for SW supplier
specific.
DCM_SUPPLIER_6 0xF5 Reserved for SW supplier
specific.
DCM_SUPPLIER_7 0xF6 Reserved for SW supplier
specific.
DCM_SUPPLIER_8 0xF7 Reserved for SW supplier
specific.
DCM_SUPPLIER_9 0xF8 Reserved for SW supplier
specific.
DCM_SUPPLIER_10 0xF9 Reserved for SW supplier
specific.
DCM_SUPPLIER_11 0xFA Reserved for SW supplier
specific.
DCM_SUPPLIER_12 0xFB Reserved for SW supplier
specific.
DCM_SUPPLIER_13 0xFC Reserved for SW supplier
specific.
DCM_SUPPLIER_14 0xFD Reserved for SW supplier
specific.
DCM_SUPPLIER_15 0xFE Reserved for SW supplier
specific.
Description Protocol type definition
Variation –
Available via Rte_Dcm_Type.h

c()

8.8.1.6 Dcm_NegativeResponseCodeType

[SWS_Dcm_00980] d
Name Dcm_NegativeResponseCodeType
Kind Type
Derived from uint8
DCM_POS_RESP 0x00 PR
range of values 0x01..0x0F 0x01..0x0F ISOSAERESRVD
reserved by ISO 14229
5

304 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
DCM_E_GENERALREJECT 0x10 GR
DCM_E_ 0x11 SNS
SERVICENOTSUPPORTED
DCM_E_SUBFUNCTIONNOT- 0x12 SFNS
SUPPORTED
DCM_E_ 0x13 IMLOIF
INCORRECTMESSAGE-
LENGTHORINVALIDFORMAT
DCM_E_RESPONSETOOLONG 0x14 RTL
range of values 0x15..0x20 0x15..0x20 ISOSAERESRVD
reserved by ISO 14229
DCM_E_ 0x21 BRR
BUSYREPEATREQUEST
DCM_E_ 0x22 CNC
CONDITIONSNOTCORRECT
value 0x23 reserved by ISO 0x23 ISOSAERESRVD
14229
DCM_E_ 0x24 RSE
REQUESTSEQUENCEERROR
DCM_E_NORESPONSEFROM- 0x25 NRFSC
SUBNETCOMPONENT
DCM_E_ 0x26 FPEORA
FAILUREPREVENTSEXECU-
TIONOFREQUESTEDACTION
range of values 0x27..0x30 0x27..0x30 ISOSAERESRVD
reserved by ISO 14229
DCM_E_ 0x31 ROOR
REQUESTOUTOFRANGE
value 0x32 reserved by ISO 0x32 ISOSAERESRVD
14229
DCM_E_ 0x33 SAD
SECURITYACCESSDENIED
value 0x34 reserved by ISO 0x34 ISOSAERESRVD
14229
DCM_E_INVALIDKEY 0x35 IK
DCM_E_ 0x36 ENOA
EXCEEDNUMBEROFATTEMPTS
DCM_E_REQUIREDTIMEDE- 0x37 RTDNE
LAYNOTEXPIRED
range of values 0x38..0x4F 0x38..0x4F RBEDLSD
reserved by ISO 15764
range of values 0x50..0x6F 0x50..0x6F ISOSAERESRVD
reserved by ISO 14229
DCM_E_UPLOADDOWNLOAD- 0x70 UDNA
NOTACCEPTED
DCM_E_ 0x71 TDS
TRANSFERDATASUSPENDED
DCM_E_GENERALPROGRAM- 0x72 GPF
MINGFAILURE
DCM_E_WRONGBLOCKSE- 0x73 WBSC
QUENCECOUNTER
range of values 0x74..0x77 0x74..0x77 ISOSAERESRVD
reserved by ISO 14229
5

305 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
range of values 0x79..0x7D 0x79..0x7D ISOSAERESRVD
reserved by ISO 14229
DCM_E_ 0x7E SFNSIAS
SUBFUNCTIONNOTSUPPORTE-
DINACTIVESESSION
DCM_E_SERVICENOTSUP- 0x7F SNSIAS
PORTEDINACTIVESESSION
value 0x80 reserved by ISO 0x80 ISOSAERESRVD
14229
DCM_E_RPMTOOHIGH 0x81 RPMTH
DCM_E_RPMTOOLOW 0x82 RPMTL
DCM_E_ENGINEISRUNNING 0x83 EIR
DCM_E_ 0x84 EINR
ENGINEISNOTRUNNING
DCM_E_ 0x85 ERTTL
ENGINERUNTIMETOOLOW
DCM_E_ 0x86 TEMPTH
TEMPERATURETOOHIGH
DCM_E_ 0x87 TEMPTL
TEMPERATURETOOLOW
DCM_E_ 0x88 VSTH
VEHICLESPEEDTOOHIGH
DCM_E_ 0x89 VSTL
VEHICLESPEEDTOOLOW
DCM_E_THROTTLE_ 0x8A TPTH
PEDALTOOHIGH
DCM_E_THROTTLE_ 0x8B TPTL
PEDALTOOLOW
DCM_E_TRANSMISSION- 0x8C TRNIN
RANGENOTINNEUTRAL
DCM_E_TRANSMISSION- 0x8D TRNIG
RANGENOTINGEAR
value 0x8E reserved by ISO 0x8E ISOSAERESRVD
14229
DCM_E_BRAKESWITCH_ 0x8F BSNC
NOTCLOSED
DCM_E_ 0x90 SLNIP
SHIFTERLEVERNOTINPARK
DCM_E_TORQUECONVERTER- 0x91 TCCL
CLUTCHLOCKED
DCM_E_VOLTAGETOOHIGH 0x92 VTH
DCM_E_VOLTAGETOOLOW 0x93 VTL
range of values 0x94..0xEF 0x94..0xEF RFSCNC
reserved by ISO 14229
DCM_E_VMSCNC_0 0xF0 VMSCNC
DCM_E_VMSCNC_1 0xF1 VMSCNC1
DCM_E_VMSCNC_2 0xF2 VMSCNC2
DCM_E_VMSCNC_3 0xF3 VMSCNC3
DCM_E_VMSCNC_4 0xF4 VMSCNC4
DCM_E_VMSCNC_5 0xF5 VMSCNC5
5

306 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
DCM_E_VMSCNC_6 0xF6 VMSCNC6
DCM_E_VMSCNC_7 0xF7 VMSCNC7
DCM_E_VMSCNC_8 0xF8 VMSCNC8
DCM_E_VMSCNC_9 0xF9 VMSCNC9
DCM_E_VMSCNC_A 0xFA VMSCNCA
DCM_E_VMSCNC_B 0xFB VMSCNCB
DCM_E_VMSCNC_C 0xFC VMSCNCC
DCM_E_VMSCNC_D 0xFD VMSCNCD
DCM_E_VMSCNC_E 0xFE VMSCNCE
value 0xFF reserved by ISO 0xFF ISOSAERESRVD
14229
Description This Table of available Negative Response Codes represents the allowed Response Codes an
AUTOSAR SW Component shall return after a function call. For the allowed NRC of the executed
Service ID please refer to the specification of the service in ISO14229-1 (UDS) and ISO15031-5
(OBD/CARB) (see chapter 4.2.4 Response code parameter definition Table 12).
Variation –
Available via Rte_Dcm_Type.h

c()

8.8.1.7 Dcm_DataElementType_{Data}Type

[SWS_Dcm_91051] d
Name Dcm_DataElement_{Data}Type
Kind Type
Derived from Basetype Variation
Dcm_DataElement_{Data}_Array (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
Type Data.?DcmDspDataType)} == ([S|U]INT[8|16|32]|FLOAT)_N)
|| ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
Pid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPid
DataType)} == ([S|U]INT[8|16|32]|FLOAT)_N))
Dcm_DataElement_{Data} (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
_PrimitiveType Data.?DcmDspDataType)} ==
(BOOLEAN|[S|U]INT[8|16|32]|FLOAT)) || ({ecuc(Dcm/?Dcm
ConfigSet/?DcmDsp/?DcmDspPid/?DcmDspPidData/?Dcm
DspPidService01.?DcmDspPidDataType)} ==
(BOOLEAN|[S|U]INT[8|16|32]|FLOAT)))
Description Common description for S/R and C/S data elements.
Variation (({Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort == USE_DATA_ELEMENT_
SPECIFIC_INTERFACES}) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspData
UsePort)} == USE_DATA_SENDER_RECEIVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Pid/DcmDspPidData/DcmDspPidService01/DcmDspPidDataUsePort)} == USE_DATA_SENDER_
RECEIVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPid
Service01/DcmDspPidDataUsePort)} == USE_DATA_SENDER_RECEIVER_AS_SERVICE) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataUsePort)} == USE_DATA_
SENDER_RECEIVER_AS_SERVICE) ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDsp
DataUsePort)} == USE_DATA_SYNCH_CLIENT_SERVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/
5
5

307 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
4
DcmDspData.DcmDspDataUsePort)} == USE_DATA_ASYNCH_CLIENT_SERVER) || ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_ASYNCH_CLIENT_
SERVER_ERROR) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDsp
PidService01.DcmDspPidDataUsePort)} == USE_DATA_SYNCH_CLIENT_SERVER) ))
Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.SHORT-NAME)})
Available via Rte_Dcm_Type.h

c()

8.8.1.8 Dcm_DataElementType_{Data}ArrayType

[SWS_Dcm_91063] d
Name Dcm_DataElement_{Data}_ArrayType
Kind Array

Element type Type Variation

float32 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspData
Type)} == FLOAT_N) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?Dcm
DspPid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPidData
Type)} == FLOAT_N))
sint16 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspData
Type)} == SINT16_N) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?Dcm
DspPid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPidData
Type)} == SINT16_N))
sint32 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspData
Type)} == SINT32_N) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?Dcm
DspPid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPidData
Type)} == SINT32_N))
sint8 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspData
Type)} == SINT8_N) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
Pid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPidDataType)}
== SINT8_N))
uint16 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspData
Type)} == UINT16_N) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?Dcm
DspPid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPidData
Type)} == UINT16_N))
uint32 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspData
Type)} == UINT32_N) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?Dcm
DspPid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPidData
Type)} == UINT32_N))
uint8 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspData
Type)} == UINT8_N) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
Pid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPidDataType)}
== UINT8_N))
Size –
Description –
5

308 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Variation ((({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspDataType)} ==
([S|U]INT[8|16|32]|FLOAT)_N) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspPid/?DcmDsp
PidData/?DcmDspPidService01.?DcmDspPidDataType)} == ([S|U]INT[8|16|32]|FLOAT)_N))
&&({Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort == USE_DATA_ELEMENT_
SPECIFIC_INTERFACES}) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspData
UsePort)} == USE_DATA_SENDER_RECEIVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Pid/DcmDspPidData/DcmDspPidService01/DcmDspPidDataUsePort)} == USE_DATA_SENDER_
RECEIVER) ||({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPid
Service01/DcmDspPidDataUsePort)} == USE_DATA_SENDER_RECEIVER_AS_SERVICE) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataUsePort)} == USE_DATA_
SENDER_RECEIVER_AS_SERVICE) ||({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.Dcm
DspDataUsePort)} == USE_DATA_SYNCH_CLIENT_SERVER) || ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_ASYNCH_CLIENT_SERVER) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
ASYNCH_CLIENT_SERVER_ERROR) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/Dcm
DspPidData/DcmDspPidService01.DcmDspPidDataUsePort)} == USE_DATA_SYNCH_CLIENT_
SERVER)))
Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.SHORT-NAME)})
Available via Rte_Dcm_Type.h

c()

8.8.1.9 Dcm_DataElementType_{Data}PrimitiveType

[SWS_Dcm_91062] d
Name Dcm_DataElement_{Data}_PrimitiveType
Kind Type
Basetype Variation
boolean (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
Data.?DcmDspDataType)} == BOOLEAN) ||
({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspPid/?Dcm
DspPidData/?DcmDspPidService01.?DcmDspPidData
Type)} == BOOLEAN))
float32 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
Data.?DcmDspDataType)} == FLOAT) || ({ecuc(Dcm/?Dcm
ConfigSet/?DcmDsp/?DcmDspPid/?DcmDspPidData/?Dcm
DspPidService01.?DcmDspPidDataType)} == FLOAT))
sint16 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
Data.?DcmDspDataType)} == SINT16) || ({ecuc(Dcm/?Dcm
ConfigSet/?DcmDsp/?DcmDspPid/?DcmDspPidData/?Dcm
DspPidService01.?DcmDspPidDataType)} == SINT16))
sint32 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
Data.?DcmDspDataType)} == SINT32) || ({ecuc(Dcm/?Dcm
ConfigSet/?DcmDsp/?DcmDspPid/?DcmDspPidData/?Dcm
DspPidService01.?DcmDspPidDataType)} == SINT32))
sint8 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
Data.?DcmDspDataType)} == SINT8) || ({ecuc(Dcm/?Dcm
ConfigSet/?DcmDsp/?DcmDspPid/?DcmDspPidData/?Dcm
DspPidService01.?DcmDspPidDataType)} == SINT8))
5

309 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
uint16 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
Data.?DcmDspDataType)} == UINT16) || ({ecuc(Dcm/?Dcm
ConfigSet/?DcmDsp/?DcmDspPid/?DcmDspPidData/?Dcm
DspPidService01.?DcmDspPidDataType)} == UINT16))
uint32 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
Data.?DcmDspDataType)} == UINT32) || ({ecuc(Dcm/?Dcm
ConfigSet/?DcmDsp/?DcmDspPid/?DcmDspPidData/?Dcm
DspPidService01.?DcmDspPidDataType)} == UINT32))
uint8 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
Data.?DcmDspDataType)} == UINT8) || ({ecuc(Dcm/?Dcm
ConfigSet/?DcmDsp/?DcmDspPid/?DcmDspPidData/?Dcm
DspPidService01.?DcmDspPidDataType)} == UINT8))
Description –
Variation ((({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspDataType)} ==
(BOOLEAN|[S|U]INT[8|16|32]|FLOAT)) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
Pid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPidDataType)} ==
(BOOLEAN|[S|U]INT[8|16|32]|FLOAT))) &&({Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidUsePort == USE_DATA_ELEMENT_SPECIFIC_INTERFACES}) && (({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspData/DcmDspDataUsePort)} == USE_DATA_SENDER_RECEIVER) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDsp
PidDataUsePort)} == USE_DATA_SENDER_RECEIVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPidDataUsePort)} == USE_DATA_
SENDER_RECEIVER_AS_SERVICE) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/Dcm
DspDataUsePort)} == USE_DATA_SENDER_RECEIVER_AS_SERVICE) ||({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_SYNCH_CLIENT_SERVER) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
ASYNCH_CLIENT_SERVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == USE_DATA_ASYNCH_CLIENT_SERVER_ERROR) || ({ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01.DcmDspPidDataUsePort)} == USE_
DATA_SYNCH_CLIENT_SERVER)))
Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.SHORT-NAME)})
Available via Rte_Dcm_Type.h

c()

8.8.1.10 Dcm_DataArrayTypeUint8_{Data}Type

[SWS_Dcm_01121] d
Name Dcm_DataArrayTypeUint8_{Data}Type
Kind Array Element type uint8
Size (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataByteSize)}) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.DcmDspPidDataByteSize)})) Elements
Description –
Variation (( {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_DATA_
ELEMENT_SPECIFIC_INTERFACES) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Data.DcmDspDataType)} == UINT8_N) ||({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.Dcm
DspDataType)} == UINT8_DYN) ||({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPid
Data/DcmDspPidService01.DcmDspPidDataType)} == UINT8_N))
Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.SHORT-NAME)})
5

310 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Available via Rte_Dcm_Type.h

c()

8.8.1.11 {DID}_Struct_DataType

This data type has a different modeling as other data types. The
{DID}_Struct_DataType datatype is modeled as prosa text only. At the time this
specification was created there are no means to visualize this datatype with existing
AUTOSAR tooling as table as all the other data types. Still AUTOSAR allows modeling
such data types. Simply that they cannot be shown here as table.
[SWS_Dcm_91056] d
Name {DID}_Struct_DataType
Kind Structure
Description The elements of this structure data type is a composition of all DcmDspDataElement of the Dcm
DspDid. Example: A DID with the 3 data elements uint32 data1, sint8 data2 and sint16 data 3,
has a structure definition of struct { uint32 data1, sint8 data2, sint16 data 3}.
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == ((USE_ATOMIC_
SENDER_RECEIVER_INTERFACE|| USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_
SERVICE) || USE_ATOMIC_NV_DATA_INTERFACE))
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})
Available via Rte_Dcm_Type.h

c()

8.8.1.12 Dcm_RangeArray_{Range}Type

[SWS_Dcm_01012] d
Name Dcm_RangeArray_{Range}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRangeMaxDataLength)} Elements
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange.DcmDspDidRangeUsePort)} == TRUE
Range = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

311 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.1.13 Dcm_InfoTypeServicesArray_{VehInfoData}Type

[SWS_Dcm_01013] d
Name Dcm_InfoTypeServicesArray_{VehInfoData}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfoData.DcmDspVehInfoData
Size)} Elements
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfoData/DcmDspVehInfoData
UsePort)} == TRUE
VehInfoData = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfo
Data.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.14 Dcm_RequestControlServicesInArray_{Tid}Type

[SWS_Dcm_01014] d
Name Dcm_RequestControlServicesInArray_{Tid}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestControl.DcmDspRequestControlInBuffer
Size)} Elements
Description –
Variation Tid = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestControl.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.15 Dcm_RequestControlServicesOutArray_{Tid}Type

[SWS_Dcm_01015] d
Name Dcm_RequestControlServicesOutArray_{Tid}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestControl.DcmDspRequestControlOutBuffer
Size)} Elements
Description –
Variation Tid = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestControl.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

312 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.1.16 Dcm_ScalingInfoArray_{Data}Type

[SWS_Dcm_01017] d
Name Dcm_ScalingInfoArray_{Data}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDataInfo.DcmDspDataScalingInfoSize)} Elements
Description –
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
ASYNCH_CLIENT_SERVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == USE_DATA_SYNCH_CLIENT_SERVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspData.DcmDspDataUsePort)} == USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData->DcmDspDataInfoRef.DcmDspDataScalingInfo
Size)} != NULL)
Data = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.17 Dcm_RequestDataOut_{Routine}_{Signal}PrimitivType

[SWS_Dcm_01018] d
Name Dcm_RequestDataOut_{Routine}_{Signal}PrimitivType
Kind Type
Basetype Variation
float32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRequestRoutineResults/DcmDspRequestRoutine
ResultsOut/DcmDspRequestRoutineResultsOutSignal.Dcm
DspRoutineSignalType)} == FLOAT
sint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRequestRoutineResults/DcmDspRequestRoutine
ResultsOut/DcmDspRequestRoutineResultsOutSignal.Dcm
DspRoutineSignalType)} == SINT16
sint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRequestRoutineResults/DcmDspRequestRoutine
ResultsOut/DcmDspRequestRoutineResultsOutSignal.Dcm
DspRoutineSignalType)} == SINT32
sint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRequestRoutineResults/DcmDspRequestRoutine
ResultsOut/DcmDspRequestRoutineResultsOutSignal.Dcm
DspRoutineSignalType)} == SINT8
uint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRequestRoutineResults/DcmDspRequestRoutine
ResultsOut/DcmDspRequestRoutineResultsOutSignal.Dcm
DspRoutineSignalType)} == UINT16
uint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRequestRoutineResults/DcmDspRequestRoutine
ResultsOut/DcmDspRequestRoutineResultsOutSignal.Dcm
DspRoutineSignalType)} == UINT32
5

313 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
uint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRequestRoutineResults/DcmDspRequestRoutine
ResultsOut/DcmDspRequestRoutineResultsOutSignal.Dcm
DspRoutineSignalType)} == UINT8
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutineSignal
Type)} == [U|S]INT[8|16|32]|FLOAT) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/
DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.18 Dcm_RequestDataIn_{Routine}_{Signal}PrimitiveType

[SWS_Dcm_91054] d
Name Dcm_RequestDataIn_{Routine}_{Signal}PrimitiveType
Kind Type

Derived from Basetype Variation

float32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRequestRoutineResults/DcmDspRequestRoutine
ResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDsp
RoutineSignalType)} == FLOAT
sint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRequestRoutineResults/DcmDspRequestRoutine
ResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDsp
RoutineSignalType)} == SINT16
sint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRequestRoutineResults/DcmDspRequestRoutine
ResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDsp
RoutineSignalType)} == SINT32
sint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRequestRoutineResults/DcmDspRequestRoutine
ResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDsp
RoutineSignalType)} == SINT8
uint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRequestRoutineResults/DcmDspRequestRoutine
ResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDsp
RoutineSignalType)} == UINT16
uint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRequestRoutineResults/DcmDspRequestRoutine
ResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDsp
RoutineSignalType)} == UINT32
uint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRequestRoutineResults/DcmDspRequestRoutine
ResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDsp
RoutineSignalType)} == UINT8
5

314 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDspRoutineSignalType)}
== [U|S]INT[8|16|32]|FLOAT)&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.19 Dcm_RequestDataOut_{Routine}_{Signal}Type

[SWS_Dcm_91040] d
Name Dcm_RequestDataOut_{Routine}_{Signal}Type
Kind Type
Derived from Basetype Variation
Dcm_RequestDataOut_{Routine} ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
_{Signal}PrimitivType DspRequestRoutineResults/DcmDspRequestRoutine
ResultsOut/DcmDspRequestRoutineResultsOutSignal.Dcm
DspRoutineSignalType)} == ([U|S]INT[8|16|32]|FLOAT))
Dcm_RequestDataOut_{Routine} ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
_{Signal}ArrayType DspRequestRoutineResults/DcmDspRequestRoutine
ResultsOut/DcmDspRequestRoutineResultsOutSignal.Dcm
DspRoutineSignalType)} == ([U|S]INT[8|16|32]|FLOAT)_N)
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.20 Dcm_RequestDataIn_{Routine}_{Signal}Type

[SWS_Dcm_91052] d
Name Dcm_RequestDataIn_{Routine}_{Signal}Type
Kind Type
Derived from Basetype Variation
5

315 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Dcm_RequestDataIn_{Routine}_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
Signal}PrimitiveType DspRequestRoutineResults/DcmDspRequestRoutine
ResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDsp
RoutineSignalType)} == ([U|S]INT[8|16|32|FLOAT)])
Dcm_RequestDataIn_{Routine}_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
Signal}ArrayType DspRequestRoutineResults/DcmDspRequestRoutine
ResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDsp
RoutineSignalType)} == ([U|S]INT[8|16|32]|FLOAT)_N)
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.21 Dcm_RequestDataOut_{Routine}_{Signal}ArrayType

[SWS_Dcm_91041] d
Name Dcm_RequestDataOut_{Routine}_{Signal}ArrayType
Kind Array

Element type Type Variation

float32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.DcmDspRoutineSignalType)} == FLOAT_N)
sint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.DcmDspRoutineSignalType)} == SINT16_N)
sint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.DcmDspRoutineSignalType)} == SINT32_N)
sint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.DcmDspRoutineSignalType)} == SINT8_N)
uint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.DcmDspRoutineSignalType)} == UINT16_N)
uint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.DcmDspRoutineSignalType)} == UINT32_N)
uint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.DcmDspRoutineSignalType)} == UINT8_N)
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutineParameter
Size)} Elements
Description –
5

316 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutineSignal
Type)} == ([U|S]INT[8|16|32]|FLOAT)_N) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/
DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.22 Dcm_RequestDataIn_{Routine}_{Signal}ArrayType

[SWS_Dcm_91055] d
Name Dcm_RequestDataIn_{Routine}_{Signal}ArrayType
Kind Array

Element type Type Variation

float32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == FLOAT_N
sint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == SINT16_N
sint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == SINT32_N
sint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == SINT8_N
uint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == UINT16_N
uint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == UINT32_N
uint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == UINT8_N
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDspRoutineParameter
Size)} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDspRoutineSignalType)}
== ([U|S]INT[8|16|32]|FLOAT)_N)&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
5

317 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Available via Rte_Dcm_Type.h

c()

8.8.1.23 Dcm_RequestFlexibleOutArrayData_{Routine}_{Signal}Type

[SWS_Dcm_01019] d
Name Dcm_RequestFlexibleOutArrayData_{Routine}_{Signal}Type
Kind Array Element type uint8
Size {(ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutineParameter
Size} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutineSignal
Type)} == VARIABLE_LENGTH)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.24 Dcm_RequestFlexibleInArrayData_{Routine}_{Signal}Type

[SWS_Dcm_91053] d
Name Dcm_RequestFlexibleInArrayData_{Routine}_{Signal}Type
Kind Array Element type uint8
Size {(ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDspRoutineParameter
Size} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDspRoutineSignalType)}
== VARIABLE_LENGTH)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

318 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.1.25 Dcm_StartDataIn_{Routine}_{Signal}PrimitivType

[SWS_Dcm_01020] d
Name Dcm_StartDataIn_{Routine}_{Signal}PrimitivType
Kind Type

Derived from Basetype Variation

float32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStartRoutine/DcmDspStartRoutineIn/DcmDspStart
RoutineInSignal.DcmDspRoutineSignalType)} == FLOAT
sint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStartRoutine/DcmDspStartRoutineIn/DcmDspStart
RoutineInSignal.DcmDspRoutineSignalType)} == SINT16
sint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStartRoutine/DcmDspStartRoutineIn/DcmDspStart
RoutineInSignal.DcmDspRoutineSignalType)} == SINT32
sint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStartRoutine/DcmDspStartRoutineIn/DcmDspStart
RoutineInSignal.DcmDspRoutineSignalType)} == SINT8
uint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStartRoutine/DcmDspStartRoutineIn/DcmDspStart
RoutineInSignal.DcmDspRoutineSignalType)} == UINT16
uint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStartRoutine/DcmDspStartRoutineIn/DcmDspStart
RoutineInSignal.DcmDspRoutineSignalType)} == UINT32
uint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStartRoutine/DcmDspStartRoutineIn/DcmDspStart
RoutineInSignal.DcmDspRoutineSignalType)} == UINT8
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
In/DcmDspStartRoutineInSignal.DcmDspRoutineSignalType)} == [U|S]INT[8|16|32]|FLOAT) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.26 Dcm_StartDataIn_{Routine}_{Signal}Type

[SWS_Dcm_91042] d
Name Dcm_StartDataIn_{Routine}_{Signal}Type
Kind Type
Basetype Variation
Dcm_StartDataIn_{Routine}_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
Signal}PrimitivType DspStartRoutine/DcmDspStartRoutineIn/DcmDspStart
RoutineInSignal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT))
5

319 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Dcm_StartDataIn_{Routine}_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
Signal}ArrayType DspStartRoutine/DcmDspStartRoutineIn/DcmDspStart
RoutineInSignal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT)_N)
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.27 Dcm_StartDataIn_{Routine}_{Signal}ArrayType

[SWS_Dcm_91043] d
Name Dcm_StartDataIn_{Routine}_{Signal}ArrayType
Kind Array

Element type Type Variation

float32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDsp
RoutineSignalType)} == FLOAT_N
sint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDsp
RoutineSignalType)} == SINT16_N)
sint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDsp
RoutineSignalType)} == SINT32_N)
sint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDsp
RoutineSignalType)} == SINT8_N)
uint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDsp
RoutineSignalType)} == UINT16_N)
uint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDsp
RoutineSignalType)} == UINT32_N)
uint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDsp
RoutineSignalType)} == UINT8_N)
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
In/DcmDspStartRoutineInSignal.DcmDspRoutineParameterSize)} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
In/DcmDspStartRoutineInSignal.DcmDspRoutineSignalType)} == ([U|S]INT[8|16|32]|FLOAT)_N)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
5

320 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Available via Rte_Dcm_Type.h

c()

8.8.1.28 Dcm_StartDataOut_{Routine}_{Signal}PrimitivType

[SWS_Dcm_01021] d
Name Dcm_StartDataOut_{Routine}_{Signal}PrimitivType
Kind Type

Derived from Basetype Variation

float32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStartRoutine/DcmDspStartRoutineOut/DcmDspStart
RoutineOutSignal.DcmDspRoutineSignalType)} == FLOAT
sint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStartRoutine/DcmDspStartRoutineOut/DcmDspStart
RoutineOutSignal.DcmDspRoutineSignalType)} == SINT16
sint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStartRoutine/DcmDspStartRoutineOut/DcmDspStart
RoutineOutSignal.DcmDspRoutineSignalType)} == SINT32
sint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStartRoutine/DcmDspStartRoutineOut/DcmDspStart
RoutineOutSignal.DcmDspRoutineSignalType)} == SINT8
uint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStartRoutine/DcmDspStartRoutineOut/DcmDspStart
RoutineOutSignal.DcmDspRoutineSignalType)} == UINT16
uint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStartRoutine/DcmDspStartRoutineOut/DcmDspStart
RoutineOutSignal.DcmDspRoutineSignalType)} == UINT32
uint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStartRoutine/DcmDspStartRoutineOut/DcmDspStart
RoutineOutSignal.DcmDspRoutineSignalType)} == UINT8
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
Out/DcmDspStartRoutineOutSignal.DcmDspRoutineSignalType)} == [U|S]INT[8|16|32]|FLOAT) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.29 Dcm_StartDataOut_{Routine}_{Signal}Type

[SWS_Dcm_91044] d

321 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name Dcm_StartDataOut_{Routine}_{Signal}Type
Kind Type
Derived from Basetype Variation
Dcm_StartDataOut_{Routine}_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
Signal}PrimitivType DspStartRoutine/DcmDspStartRoutineOut/DcmDspStart
RoutineOutSignal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT))
Dcm_StartDataOut_{Routine}_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
Signal}ArrayType DspStartRoutine/DcmDspStartRoutineOut/DcmDspStart
RoutineOutSignal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT)_N)
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.30 Dcm_StartDataOut_{Routine}_{Signal}ArrayType

[SWS_Dcm_91045] d
Name Dcm_StartDataOut_{Routine}_{Signal}ArrayType
Kind Array

Element type Type Variation

float32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.Dcm
DspRoutineSignalType)} == FLOAT_N
sint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.Dcm
DspRoutineSignalType)} == SINT16_N)
sint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.Dcm
DspRoutineSignalType)} == SINT32_N)
sint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.Dcm
DspRoutineSignalType)} == SINT8_N)
uint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.Dcm
DspRoutineSignalType)} == UINT16_N)
uint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.Dcm
DspRoutineSignalType)} == UINT32_N)
uint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.Dcm
DspRoutineSignalType)} == UINT8_N)
5

322 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
Out/DcmDspStartRoutineOutSignal.DcmDspRoutineParameterSize)} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
Out/DcmDspStartRoutineOutSignal.DcmDspRoutineSignalType)} == ([U|S]INT[8|16|32]|FLOAT)_
N) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.31 Dcm_StartFlexibleInArrayData_{Routine}_{Signal}Type

[SWS_Dcm_01022] d
Name Dcm_StartFlexibleInArrayData_{Routine}_{Signal}Type
Kind Array Element type uint8
Size {(ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
In/DcmDspStartRoutineInSignal.DcmDspRoutineParameterSize} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
In/DcmDspStartRoutineInSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.32 Dcm_StartFlexibleOutArrayData_{Routine}_{Signal}Type

[SWS_Dcm_01023] d
Name Dcm_StartFlexibleOutArrayData_{Routine}_{Signal}Type
Kind Array Element type uint8
Size {(ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
Out/DcmDspStartRoutineOutSignal.DcmDspRoutineParameterSize} Elements
Description –
5

323 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
Out/DcmDspStartRoutineOutSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.33 Dcm_StopDataIn_{Routine}_{Signal}PrimitivType

[SWS_Dcm_01024] d
Name Dcm_StopDataIn_{Routine}_{Signal}PrimitivType
Kind Type

Derived from Basetype Variation

float32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStopRoutine/DcmDspStopRoutineIn/DcmDspStop
RoutineInSignal.DcmDspRoutineSignalType)} == FLOAT
sint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStopRoutine/DcmDspStopRoutineIn/DcmDspStop
RoutineInSignal.DcmDspRoutineSignalType)} == SINT16
sint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStopRoutine/DcmDspStopRoutineIn/DcmDspStop
RoutineInSignal.DcmDspRoutineSignalType)} == SINT32
sint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStopRoutine/DcmDspStopRoutineIn/DcmDspStop
RoutineInSignal.DcmDspRoutineSignalType)} == SINT8
uint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStopRoutine/DcmDspStopRoutineIn/DcmDspStop
RoutineInSignal.DcmDspRoutineSignalType)} == UINT16
uint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStopRoutine/DcmDspStopRoutineIn/DcmDspStop
RoutineInSignal.DcmDspRoutineSignalType)} == UINT32
uint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStopRoutine/DcmDspStopRoutineIn/DcmDspStop
RoutineInSignal.DcmDspRoutineSignalType)} == UINT8
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
In/DcmDspStopRoutineInSignal.DcmDspRoutineSignalType)} == ([U|S]INT[8|16|32]|FLOAT)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

324 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.1.34 Dcm_StopDataIn_{Routine}_{Signal}Type

[SWS_Dcm_91046] d
Name Dcm_StopDataIn_{Routine}_{Signal}Type
Kind Type
Derived from Basetype Variation
Dcm_StopDataIn_{Routine}_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
Signal}PrimitivType DspStopRoutine/DcmDspStopRoutineIn/DcmDspStop
RoutineInSignal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT))
Dcm_StopDataIn_{Routine}_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
Signal}ArrayType DspStopRoutine/DcmDspStopRoutineIn/DcmDspStop
RoutineInSignal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT)_N)
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.35 Dcm_StopDataIn_{Routine}_{Signal}ArrayType

[SWS_Dcm_91047] d
Name Dcm_StopDataIn_{Routine}_{Signal}ArrayType
Kind Array
Type Variation
float32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDsp
RoutineSignalType)} == FLOAT_N
sint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDsp
RoutineSignalType)} == SINT16_N)
sint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDsp
RoutineSignalType)} == SINT32_N)
sint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDsp
RoutineSignalType)} == SINT8_N)
uint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDsp
RoutineSignalType)} == UINT16_N)
uint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDsp
RoutineSignalType)} == UINT32_N)
5

325 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
uint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDsp
RoutineSignalType)} == UINT8_N)
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
In/DcmDspStopRoutineInSignal.DcmDspRoutineParameterSize)} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
In/DcmDspStopRoutineInSignal.DcmDspRoutineSignalType)} == ([U|S]INT[8|16|32]|FLOAT)_N)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.36 Dcm_StopDataOut_{Routine}_{Signal}PrimitivType

[SWS_Dcm_01025] d
Name Dcm_StopDataOut_{Routine}_{Signal}PrimitivType
Kind Type

Derived from Basetype Variation

float32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStopRoutine/DcmDspStopRoutineOut/DcmDspStop
RoutineOutSignal.DcmDspRoutineSignalType)} == FLOAT
sint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStopRoutine/DcmDspStopRoutineOut/DcmDspStop
RoutineOutSignal.DcmDspRoutineSignalType)} == SINT16
sint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStopRoutine/DcmDspStopRoutineOut/DcmDspStop
RoutineOutSignal.DcmDspRoutineSignalType)} == SINT32
sint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStopRoutine/DcmDspStopRoutineOut/DcmDspStop
RoutineOutSignal.DcmDspRoutineSignalType)} == SINT8
uint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStopRoutine/DcmDspStopRoutineOut/DcmDspStop
RoutineOutSignal.DcmDspRoutineSignalType)} == UINT16
uint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStopRoutine/DcmDspStopRoutineOut/DcmDspStop
RoutineOutSignal.DcmDspRoutineSignalType)} == UINT32
uint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspStopRoutine/DcmDspStopRoutineOut/DcmDspStop
RoutineOutSignal.DcmDspRoutineSignalType)} == UINT8
Description –
5

326 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
Out/DcmDspStopRoutineOutSignal.DcmDspRoutineSignalType)} == [U|S]INT[8|16|32]|FLOAT) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.37 Dcm_StopDataOut_{Routine}_{Signal}Type

[SWS_Dcm_91048] d
Name Dcm_StopDataOut_{Routine}_{Signal}Type
Kind Type
Derived from Basetype Variation
Dcm_StopDataOut_{Routine}_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
Signal}PrimitivType DspStopRoutine/DcmDspStopRoutineOut/DcmDspStop
RoutineOutSignal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT))
Dcm_StopDataOut_{Routine}_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
Signal}ArrayType DspStopRoutine/DcmDspStopRoutineOut/DcmDspStop
RoutineOutSignal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT)_N)
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.38 Dcm_StopDataOut_{Routine}_{Signal}ArrayType

[SWS_Dcm_91049] d
Name Dcm_StopDataOut_{Routine}_{Signal}ArrayType
Kind Array
Type Variation
float32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.Dcm
DspRoutineSignalType)} == FLOAT_N
5

327 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
sint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.Dcm
DspRoutineSignalType)} == SINT16_N)
sint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.Dcm
DspRoutineSignalType)} == SINT32_N)
sint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.Dcm
DspRoutineSignalType)} == SINT8_N)
uint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.Dcm
DspRoutineSignalType)} == UINT16_N)
uint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.Dcm
DspRoutineSignalType)} == UINT32_N)
uint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.Dcm
DspRoutineSignalType)} == UINT8_N)
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
Out/DcmDspStopRoutineOutSignal.DcmDspRoutineParameterSize)} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
Out/DcmDspStopRoutineOutSignal.DcmDspRoutineSignalType)} == ([U|S]INT[8|16|32]|FLOAT)_
N) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.39 Dcm_StopFlexibleInArrayData_{Routine}_{Signal}Type

[SWS_Dcm_01026] d
Name Dcm_StopFlexibleInArrayData_{Routine}_{Signal}Type
Kind Array Element type uint8
Size {(ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
In/DcmDspStopRoutineInSignal.DcmDspRoutineParameterSize} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
In/DcmDspStopRoutineInSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

328 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.1.40 Dcm_StopFlexibleOutArrayData_{Routine}_{Signal}Type

[SWS_Dcm_01027] d
Name Dcm_StopFlexibleOutArrayData_{Routine}_{Signal}Type
Kind Array Element type uint8
Size {(ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
Out/DcmDspStopRoutineOutSignal.DcmDspRoutineParameterSize} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
Out/DcmDspStopRoutineOutSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.41 Dcm_KeyArray_{SecurityLevel}Type

[SWS_Dcm_01028] d
Name Dcm_KeyArray_{SecurityLevel}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurityKey
Size)} Elements
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurityUse
Port)} == USE_ASYNCH_CLIENT_SERVER
SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurity
Row.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.42 Dcm_SeedArray_{SecurityLevel}Type

[SWS_Dcm_01029] d
Name Dcm_SeedArray_{SecurityLevel}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecuritySeed
Size)} Elements
5

329 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurityUse
Port)} == USE_ASYNCH_CLIENT_SERVER
SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurity
Row.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.43 Dcm_SecurityAccessDataRecordArray_{SecurityLevel}Type

[SWS_Dcm_01159] d
Name Dcm_SecurityAccessDataRecordArray_{SecurityLevel}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp/DcmDspSecurity/DcmDspSecurityRow/DcmDsp
SecurityADRSize)} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurityUse
Port)} == USE_ASYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Security/DcmDspSecurityRow.DcmDspSecurityADRSize)} != NULL)
SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurity
Row.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()

8.8.1.44 Dcm_RequestDataArrayType

[SWS_Dcm_01165] d
Name Dcm_RequestDataArrayType
Kind Array Element type uint8
Size (MAX({ecuc(Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslProtocol
RxBufferID->DcmDslBuffer.DcmDslBufferSize)}) -1) Elements
Description –
Variation –
Available via Rte_Dcm_Type.h

c()

8.8.1.45 Dcm_ControlMask_{DID}Type

[SWS_Dcm_01320] d

330 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name Dcm_ControlMask_{DID}Type
Kind Type

Derived from Basetype Variation

Dcm_ControlMask_{Data}Array (( ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
Type DidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDsp
DidControlMaskSize)} >= 0x05) && (({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspData.DcmDspDataUsePort)} ==
(USE_DATA_ SYNCH_CLIENT_SERVER || USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_
CLIENT_SERVER_ERROR)))
uint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDsp
DidControlMaskSize)} == 0x02)
uint32 (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDsp
DidControlMaskSize)}== 0x03)||{ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/
DcmDspDidControl/DcmDspDidControlMaskSize)}== 0x04))
uint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDsp
DidControlMaskSize)} == 0x01)
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
SYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_
CLIENT_SERVER_ERROR)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlEnableMask)} == NULL)
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})
Available via Rte_Dcm_Type.h

c()

8.8.1.46 Dcm_inputOutputControlParameterType

[SWS_Dcm_01305] d
Name Dcm_InputOutputControlParameterType
Kind Type
Derived from uint8
Range DCM_RETURN_CONTROL_TO_ 0x00 returnControlToECU
ECU
DCM_RESET_TO_DEFAULT 0x01 resetToDefault
DCM_FREEZE_CURRENT_ 0x02 freezeCurrentState
STATE
DCM_SHORT_TERM_ 0x03 shortTermAdjustment
ADJUSTMENT
DCM_IDLE 0xff Idle state, no request in
processing (initial value)
5

331 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Description –
Variation –
Available via Rte_Dcm_Type.h

c()

8.8.1.47 Dcm_IOOperationRequest_{DID}Type

[SWS_Dcm_01306] d
Name Dcm_IOOperationRequest_{DID}Type
Kind Structure
Elements inputOutputControlParameter
Type Dcm_InputOutputControlParameterType
Comment –
controlEnableMask
Type Dcm_Cemr_{DID}Type
Comment –
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_
SENDER_RECEIVER_INTERFACE )) ||({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/Dcm
DspDidUsePort)} == (USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE
))&&({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDspDidInfo/Dcm
DspDidControl)} != NULL)
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})
Available via Rte_Dcm_Type.h

c()

8.8.1.48 Dcm_IOOperationResponseType

[SWS_Dcm_01307] d
Name Dcm_IOOperationResponseType
Kind Type
Derived from uint8
DCM_POSITIVE_RESPONSE 0x00 positive response (similar to E_
OK)
DCM_GENERAL_REJECT 0x10 NRC generalReject
DCM_BUSY_REPEAT_ 0x21 NRC busyRepeatRequest
REQUEST
DCM_CONDITIONS_NOT_ 0x22 NRC conditionsNotCorrect
CORRECT
5

332 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
DCM_FAILURE_PREVENTS_ 0x26 NRC FailurePreventsExecutionOf
EXECUTION RequestedAction
DCM_REQUEST_OUT_OF_ 0x31 NRC requestOutOfRange
RANGE
DCM_RESPONSE_PENDING 0x78 ResponsePending (similar to E_
PENDING)
Description –
Variation –
Available via Rte_Dcm_Type.h

c()

8.8.1.49 Dcm_DidSupportedType

[SWS_Dcm_01138] d
Name Dcm_DidSupportedType
Kind Type
Derived from uint8
Range DCM_DID_SUPPORTED 0x00 –
DCM_DID_NOT_SUPPORTED 0x01 –
Description –
Variation –
Available via Rte_Dcm_Type.h

c()

8.8.1.50 Dcm_FileAndDirNameType

[SWS_Dcm_91066] d
Name Dcm_FileAndDirNameType
Kind Array Element type uint8
Size ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer.DcmRequestFileTransferMax
FileAndDirName)}) Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer/DcmRequestFileTransferUse
Port)} == TRUE)
Available via Rte_Dcm_Type.h

c()

333 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.1.51 Dcm_ResponseDataArrayType

[SWS_Dcm_91064] d
Name Dcm_ResponseDataArrayType
Kind Array Element type uint8
Size (MAX({ecuc(Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslProtocol
TxBufferRef->DcmDslBuffer.DcmDslBufferSize)}) -1) Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer/DcmRequestFileTransferUse
Port)} == TRUE)
Available via Rte_Dcm_Type.h

c()

8.8.1.52 Dcm_AuthenticationRoleType

[SWS_Dcm_91068] d
Name Dcm_AuthenticationRoleType
Kind Array Element type uint8
Size ({ecuc(Dcm/DcmDsp/DcmDspAuthentication.DcmDspAuthenticationRoleSize)}) Elements
Description –
Variation –
Available via Rte_Dcm_Type.h

c()

8.8.1.53 Dcm_ControlMask_{Data}ArrayType

[SWS_Dcm_91050] d
Name Dcm_ControlMask_{Data}ArrayType
Kind Array Element type uint8
Size ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidControlMaskSize)}) Elements
Description –
Variation (( ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidControlMaskSize)} >= 0x05) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspData.DcmDspDataUsePort)} == (USE_DATA_ SYNCH_CLIENT_SERVER || USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)))
Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
Available via Rte_Dcm_Type.h

c()

334 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.1.54 Dcm_Cemr_{DID}Type

[SWS_Dcm_91087] d
Name Dcm_Cemr_{DID}Type
Kind Bitfield
Derived from Dcm_ControlMask_{DID}Type
Elements Variable bit
Kind bit
Name ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidControl. DcmDspDidControlEnable
Mask.SHORT-NAME)}
Mask 2ˆ (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDsp
DidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)} * 8 - 1) - {ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDid
Control/DcmDspDidControlEnableMask/DcmDspDidControlMaskBitPosition)})
Descrip- Bitmask of data element in control enable mask record.
tion
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidControl/DcmDspDidControlEnableMask)} !=
NULL)
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)}
Available via Rte_Dcm_Type.h

c()
The Dcm_Cemr_Type data type defines a bitfield text table with a single mask entry
for each valid bit in the control enable mask record. A value of 0 in the DcmDspDid-
ControlMaskBitPosition represents the most significant bit in the most significant
byte of the control enable mask. Therefore it is mapped to Bit 7 (0x80) of the first byte
of the control enable mask. In a two byte CEMR the bit position 0 would map to 0x8000,
the bit position 1 would map to 0x4000, ... . Also this is a unusual representation it
helps to keep the bits stable if the size of the CEMR is changed. The definition of the
bits is directly defined by DcmDspDidControlEnableMask.

8.8.2 Sender-Receiver-Interfaces

Using the concepts of the SW-C template, the interface is defined as follows if Sender-
Receiver interface is used (DcmDspDataUsePort set to
USE_DATA_SENDER_RECEIVER ||USE_DATA_SENDER_RECEIVER_AS_SERVICE):

8.8.2.1 DataServices_{DID}

[SWS_Dcm_91057] d

335 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DataServices_{DID}
Comment –
IsService ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_ATOMIC_
SENDER_RECEIVER_INTERFACE_AS_SERVICE)
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_
SENDER_RECEIVER_INTERFACE) ||({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/Dcm
DspDidUsePort)} == (USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE))
DID = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)}
Data Elements data
Type {DID}_Struct_DataType
Variation DID = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)}

c(RS_Diag_04218)

8.8.2.2 DataServices_{Data}

[SWS_Dcm_00687] d
Name DataServices_{Data}
Comment –
IsService (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataUsePort)} == USE_DATA_
SENDER_RECEIVER_AS_SERVICE) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/Dcm
DspPidData/DcmDspPidService01/DcmDspPidDataUsePort)} == USE_DATA_SENDER_
RECEIVER_AS_SERVICE))
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_DATA_
ELEMENT_SPECIFIC_INTERFACES)&&({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/
DcmDspDataUsePort)} == (USE_DATA_SENDER_RECEIVER ||USE_DATA_SENDER_
RECEIVER_AS_SERVICE))) ||({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPid
Data/DcmDspPidService01/DcmDspPidDataUsePort)} ==(USE_DATA_SENDER_RECEIVER
||USE_DATA_SENDER_RECEIVER_AS_SERVICE))
Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.SHORT-NAME})
Data Elements data
Type Dcm_DataElement_{Data}Type
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPid
Data.SHORT-NAME)})

c()

8.8.2.3 IOControlRequest_{DID}

[SWS_Dcm_01308] d

336 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name IOControlRequest_{DID}
Comment Attention: controlState is only valid in case of IOOperationRequest is set to shortTerm
Adjustment.
The DCM provides a byte stream which could be transformed via transformer into an complex
type.
IsService true
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDspDidInfo/Dcm
DspDidControl/DcmDspDidShortTermAdjustment)} == True) && ({ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDid
ControlMask)} == DCM_CONTROLMASK_EXTERNAL)))
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})

Data Elements underControl

Type Dcm_Cemr_{DID}Type
Variation –
IOOperationRequest
Type Dcm_IOOperationRequest_{DID}Type
Variation DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})
controlState
Type {DID}_Struct_DataType
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidShortTermAdjustment)} == True)
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})

c()

8.8.2.4 IOControlResponse_{DID}

[SWS_Dcm_01309] d
Name IOControlResponse_{DID}
Comment –
IsService true
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} ==(USE_ATOMIC_
SENDER_RECEIVER_INTERFACE || USE_ATOMIC_SENDER_RECEIVER_INTERFACE_
AS_SERVICE))) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDspDidInfo/Dcm
DspDidControl)} != NULL))
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})
Data Elements IOOperationResponse
Type Dcm_IOOperationResponseType
Variation –

c()

337 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.3 Client-Server-Interfaces

8.8.3.1 SecurityAccess_{SecurityLevel}

Provides functions required for the UDS Service SecurityAccess (see [

SWS_Dcm_00323],[SWS_Dcm_00862] and [SWS_Dcm_00863]).
Using the concepts of the SW-C template, the interface is defined as fol-
lows if ClientServer interface is used (DcmDspSecurityUsePort set to or
USE_ASYNCH_CLIENT_SERVER):
[SWS_Dcm_00685] d
Name SecurityAccess_{SecurityLevel}
Comment –
IsService true
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurity
UsePort)} == USE_ASYNCH_CLIENT_SERVER
SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurity
Row.SHORT-NAME)}
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
10 DCM_E_PENDING Request is not yet finished. Further call(s) required
to finish.
11 DCM_E_COMPARE_ Key did not match.
KEY_FAILED

Operation CompareKey
Comment –
Variation –
Key
Parameters
Type Dcm_KeyArray_{SecurityLevel}Type
Direction IN
Comment Key, which needs to be compared
Variation SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDsp
SecurityRow.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment return Error Code
Variation –
5

338 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_COMPARE_KEY_FAILED

Operation GetSecurityAttemptCounter
Comment Restore the attempt counter from the application
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurity
AttemptCounterEnabled)} == TRUE
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
AttemptCounter
Type uint8
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation GetSeed
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurity
ADRSize)} == NULL)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
Seed
Type Dcm_SeedArray_{SecurityLevel}Type
Direction OUT
Comment Pointer for provided seed
Variation SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDsp
SecurityRow.SHORT-NAME)}
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

339 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Operation GetSeed
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurity
ADRSize)} != NULL)
SecurityAccessDataRecord
Parameters
Type Dcm_SecurityAccessDataRecordArray_{SecurityLevel}Type
Direction IN
Comment –
Variation SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDsp
SecurityRow.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
Seed
Type Dcm_SeedArray_{SecurityLevel}Type
Direction OUT
Comment Pointer for provided seed
Variation SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDsp
SecurityRow.SHORT-NAME)}
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation SetSecurityAttemptCounter
Comment Store the attempt counter in the application
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurity
AttemptCounterEnabled)} == TRUE
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
AttemptCounter
Type uint8
Direction IN
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

c()

340 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.3.2 DataServices_{Data}

Using the concepts of the SW-C template, the interface is defined as fol-
lows if ClientServer interface is used (DcmDspDataUsePort set to USE_-
DATA_SYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER or
USE_DATA_ASYNCH_CLIENT_SERVER_ERROR):
[SWS_Dcm_00686] d
Name DataServices_{Data}
Comment –
IsService true
Variation ((( {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_DATA_
ELEMENT_SPECIFIC_INTERFACES)) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Data.DcmDspDataUsePort)} == USE_DATA_SYNCH_CLIENT_SERVER) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} ==USE_DATA_ASYNCH_CLIENT_
SERVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)}
==USE_DATA_ASYNCH_CLIENT_SERVER_ERROR) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspPid/DcmDspPidData/DcmDspPidService01.DcmDspPidDataUsePort)} ==USE_DATA_
SYNCH_CLIENT_SERVER) )
Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.SHORT-NAME)})
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
10 DCM_E_PENDING Request is not yet finished. Further call(s) required
to finish.

Operation ConditionCheckRead
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidRead)} != NULL) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataConditionCheckReadFnc
Used)} == TRUE)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

341 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Operation ConditionCheckRead
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidRead)} != NULL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
ConditionCheckReadFncUsed)} == TRUE)
Parameters ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation FreezeCurrentState
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidFreeze
CurrentState)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} != DCM_
CONTROLMASK_EXTERNAL)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation FreezeCurrentState
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidFreeze
CurrentState)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL)
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
5

342 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Variation –
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation FreezeCurrentState
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidFreezeCurrentState)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} != DCM_CONTROLMASK_EXTERNAL)
Parameters ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation FreezeCurrentState
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidFreezeCurrentState)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL)
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
5

343 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Variation –
Possible Errors E_OK
E_NOT_OK

Operation GetScalingInformation
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataInfoRef->DcmDspDataScaling
InfoSize)} != NULL)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ScalingInfo
Type Dcm_ScalingInfoArray_{Data}Type
Direction OUT
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation GetScalingInformation
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDsp
DataInfoRef->DcmDspDataScalingInfoSize)} != NULL)
ScalingInfo
Parameters
Type Dcm_ScalingInfoArray_{Data}Type
Direction OUT
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

344 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Operation ReadData
Comment The server is not allowed to return E_NOT_OK, but shall always provide a valid data value (e.g.
a default/replacement value in an error-case) to Dcm/Dem nevertheless the signature of the
operation includes E_NOT_OK to ensure compatibility between server runnable and RTE Call
API, since the RTE may return negative Std_Return values in certain cases (e.g. partition of
server stopped)
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
ASYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/Dcm
DspDidRead)} != NULL)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
Data
Type Dcm_DataElement_{Data}Type
Direction OUT
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPid
Data.SHORT-NAME)})
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ReadData
Comment The server is not allowed to return E_NOT_OK, but shall always provide a valid data value (e.g.
a default/replacement value in an error-case) to Dcm/Dem nevertheless the signature of the
operation includes E_NOT_OK to ensure compatibility between server runnable and RTE Call
API, since the RTE may return negative Std_Return values in certain cases (e.g. partition of
server stopped)
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
ASYNCH_CLIENT_SERVER_ERROR) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid
Info/DcmDspDidRead)} != NULL)
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
Data
Type Dcm_DataElement_{Data}Type
Direction OUT
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPid
Data.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
5

345 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ReadData
Comment The server is not allowed to return E_NOT_OK, but shall always provide a valid data value (e.g.
a default/replacement value in an error-case) to Dcm/Dem nevertheless the signature of the
operation includes E_NOT_OK to ensure compatibility between server runnable and RTE Call
API, since the RTE may return negative Std_Return values in certain cases (e.g. partition of
server stopped)
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/Dcm
DspDidRead)} != NULL) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/
DcmDspPidService01.DcmDspPidDataUsePort)} == USE_DATA_SYNCH_CLIENT_SERVER))
Parameters Data
Type Dcm_DataElement_{Data}Type
Direction OUT
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPid
Data.SHORT-NAME)})
Possible Errors E_OK
E_NOT_OK

Operation ReadDataLength
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidRead)} != NULL) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataType} == UINT8_DYN)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataLength
Type uint16
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

346 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Operation ReadDataLength
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidRead)} != NULL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataType}
== UINT8_DYN)
Parameters DataLength
Type uint16
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ResetToDefault
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidResetTo
Default)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} != DCM_
CONTROLMASK_EXTERNAL)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ResetToDefault
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidResetTo
Default)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL)
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
5

347 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Variation –
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ResetToDefault
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidResetToDefault)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} != DCM_CONTROLMASK_EXTERNAL)
Parameters ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ResetToDefault
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidResetToDefault)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL)
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
5

348 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ReturnControlToECU
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
SYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER || USE_DATA_
ASYNCH_CLIENT_SERVER_ERROR)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid
Info/DcmDspDidControl/DcmDspDidFreezeCurrentState)} == TRUE) || ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidResetToDefault)} == TRUE) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShort
TermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} != DCM_
CONTROLMASK_EXTERNAL)
Parameters ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ReturnControlToECU
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidFreeze
CurrentState)} == TRUE) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDid
Control/DcmDspDidResetToDefault)} == TRUE) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidShortTermAdjustment)} == TRUE) && ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/
DcmDspDidControlMask)} == DCM_CONTROLMASK_EXTERNAL)
controlMask
Parameters
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ShortTermAdjustment
Comment –
5

349 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShort
TermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDsp
DataType} != UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} != DCM_
CONTROLMASK_EXTERNAL)
ControlStateInfo
Parameters
Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ShortTermAdjustment
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShort
TermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDsp
DataType} != UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL)
ControlStateInfo
Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
5

350 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ShortTermAdjustment
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShort
TermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDsp
DataType} == UINT8_DYN) &&({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} != DCM_
CONTROLMASK_EXTERNAL)
ControlStateInfo
Parameters Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
DataLength
Type uint16
Direction IN
Comment –
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

351 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Operation ShortTermAdjustment
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShort
TermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDsp
DataType} == UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL)
ControlStateInfo
Parameters Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
DataLength
Type uint16
Direction IN
Comment –
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ShortTermAdjustment
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidShortTermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspData.DcmDspDataType} != UINT8_DYN) &&({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} != DCM_CONTROLMASK_EXTERNAL)
ControlStateInfo
Type Dcm_DataArrayTypeUint8_{Data}Type
5

352 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ShortTermAdjustment
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidShortTermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspData.DcmDspDataType} != UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL)
ControlStateInfo
Parameters
Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ShortTermAdjustment
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidShortTermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspData.DcmDspDataType} == UINT8_DYN) &&({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} != DCM_CONTROLMASK_EXTERNAL)
ControlStateInfo
Type Dcm_DataArrayTypeUint8_{Data}Type
5

353 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
DataLength
Type uint16
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ShortTermAdjustment
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidShortTermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspData.DcmDspDataType} == UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL)
ControlStateInfo
Parameters Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
DataLength
Type uint16
Direction IN
Comment –
Variation –
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

354 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Operation WriteData
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidWrite)} != NULL) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataType} != UINT8_DYN)
Data
Parameters
Type Dcm_DataElement_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation WriteData
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidWrite)} != NULL) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataType} == UINT8_DYN)
Data
Type Dcm_DataElement_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
DataLength
Type uint16
Direction IN
Comment –
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ErrorCode
5

355 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation WriteData
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidWrite)} != NULL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataType}
!= UINT8_DYN)
Data
Parameters
Type Dcm_DataElement_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation WriteData
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidWrite)} != NULL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataType}
== UINT8_DYN)
Data
Type Dcm_DataElement_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
DataLength
Type uint16
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
5

356 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

c()
One DataServices interface will be generated for each Data of each DID/PID, with
following possible operations:

8.8.3.2.1 ReadData

ReadData allows requesting to the application a data value of a DID/PID. A ReadData

interface is defined for every data of each DID/PID with read access. The Data spe-
cific type is an array of uint8 which represents either the fix length of this Data or the
maximum possible length of this Data. If the length is variable, the operation Read-
DataLength has to provide the current valid data length of this Data.
This interface is used for UDS Service ReadDataByIdentifier and for UDS Service Read-
DataByPeriodicIdentifier (0x2A) and for UDS Service InputOutputControlByIdentifier
(0x2F).
The ReadData interface can be defined as synchronous or asynchronous according to
configuration parameter DcmDspDataUsePort. The synchronous mechanism of the
ReadData interface is compatible to the related DEM interface to allow the provider to
use the same interface for both Dcm and DEM.

8.8.3.2.2 WriteData

WriteData requests the application to write a data value of a DID. The Data specific type
is an array of uint8 which represent either the fix length of this Data or the maximum
possible length of this Data. A WriteData interface is defined for every data of each
DID with write access. This interface is used for the UDS Service WriteDataByIdentifier
(0x2E).

8.8.3.2.3 ReadDataLength

ReadDataLength requests the application to return the data length of a Data. A Read-
DataLength interface is defined for every data of each DID with variable data length.
This interface is used for UDS Service ReadDataByIdentifier and for UDS Service Read-
DataByPeriodicIdentifier (0x2A).

357 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.3.2.4 ConditionCheckRead

ConditionCheckRead requests to the application if the conditions (System state,...) to

read the Data are correct. This operation is called for all requested DIDs before re-
questing the data of each DID. A ConditionCheckRead interface is defined for every
data of each DID with read access.

8.8.3.2.5 GetScalingInformation

Request to the application for the scaling information of a Data (see

[SWS_Dcm_00394]).

8.8.3.2.6 ReturnControlToEcu

Request to the application to return control to ECU of an IOControl (see

[SWS_Dcm_00396]).

8.8.3.2.7 ResetToDefault

Request to the application to reset an IOControl to default value (see

[SWS_Dcm_00397]).

8.8.3.2.8 FreezeCurrentState

Request to the application to freeze the current state of an IOControl (see

[SWS_Dcm_00398]).

8.8.3.2.9 ShortTermAdjustment

Request to the application to adjust the IO signal (see [SWS_Dcm_00399]).

8.8.3.3 DataServices_DIDRange_{Range}

The following interface defines an operation needed to get the DID range. Using the
concepts of the SW-C template, the interface is defined as follows:
[SWS_Dcm_00769] d

358 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DataServices_DIDRange_{Range}
Comment –
IsService true
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange.DcmDspDidRangeUsePort)} == TRUE
Range = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange.SHORT-NAME)})
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
10 DCM_E_PENDING Request is not yet finished. Further call(s) required
to finish.

Operation IsDidAvailable
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange.DcmDspDidRangeHasGaps)} == TRUE
DID
Parameters
Type uint16
Direction IN
Comment –
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
supported
Type Dcm_DidSupportedType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
DCM_E_PENDING

Operation ReadDidData
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange/DcmDspDidRangeInfoRef->DcmDsp
DidRead)} != NULL)
DID
Type uint16
Direction IN
Comment –
Variation –
Data
Type Dcm_RangeArray_{Range}Type
Direction OUT
Comment –
Variation Range = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid
Range.SHORT-NAME)})
5

359 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataLength
Type uint16
Direction OUT
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ReadDidRangeDataLength
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange/DcmDspDidRangeInfoRef->DcmDsp
DidRead)} != NULL)
DID
Parameters
Type uint16
Direction IN
Comment –
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataLength
Type uint16
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

360 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Operation WriteDidData
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange/DcmDspDidRangeInfoRef->DcmDsp
DidWrite)} != NULL)
DID
Parameters Type uint16
Direction IN
Comment –
Variation –
Data
Type Dcm_RangeArray_{Range}Type
Direction IN
Comment –
Variation Range = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid
Range.SHORT-NAME)})
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataLength
Type uint16
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

c()

8.8.3.4 InfotypeServices_{VehInfoData}

The following interface defines an operation needed to get data from one or several
SW-C in order to supply OBD Service $09 (see [SWS_Dcm_00423]).
Using the concepts of the SW-C template, the interface is defined as follows:
[SWS_Dcm_00688] d

361 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name InfotypeServices_{VehInfoData}
Comment –
IsService true
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfoData/DcmDspVehInfo
DataUsePort)}==TRUE
VehInfoData = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfo
Data.SHORT-NAME)}
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
10 DCM_E_PENDING Request is not yet finished. Further call(s) required
to finish.

Operation GetInfotypeValueData
Comment –
Variation –
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataValueBuffer
Type Dcm_InfoTypeServicesArray_{VehInfoData}Type
Direction OUT
Comment –
Variation VehInfoData = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDsp
VehInfoData.SHORT-NAME)}
DataValueBufferSize
Type uint8
Direction INOUT
Comment When the function is called this parameter contains the maximum number of
data bytes that can be written to the buffer. The function returns the actual
number of written data bytes in DataValueBuffer
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

c()

8.8.3.5 RoutineServices_{RoutineName}

The following interface defines operations needed for the UDS Service Rou-
tineControl (0x31) (see [SWS_Dcm_00400], [SWS_Dcm_00401], [SWS_Dcm_00402],
[SWS_Dcm_00403], [SWS_Dcm_00404], [SWS_Dcm_00405]).
Using the concepts of the SW-C template, the interface is defined as follows:
[SWS_Dcm_00690] d

362 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name RoutineServices_{RoutineName}
Comment –
IsService true
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.DcmDspRoutineUsePort)} == TRUE
RoutineName = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
10 DCM_E_PENDING Request is not yet finished. Further call(s) required
to finish.
12 DCM_E_FORCE_RCRRP application request the transmission of a response
Response Pending (NRC 0x78)

Operation RequestResults
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/Dcm
DspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutine
SignalType)} != VARIABLE_LENGTH) &&({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine/DcmDspRequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH)
DataIn_{Signal}
Parameters
Type Dcm_RequestDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.SHORT-NAME)}Routine = {ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspRoutine.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_RequestDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
5

363 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation RequestResults
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/Dcm
DspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutine
SignalType)} == VARIABLE_LENGTH) &&({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine/DcmDspRequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH)
DataIn_{Signal}
Type Dcm_RequestDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.SHORT-NAME)}Routine = {ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspRoutine.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_RequestDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutine
Results/DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResults
OutSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataOut_{Signal}
Type Dcm_RequestFlexibleOutArrayData_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutine
Results/DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResults
OutSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
currentDataLength
5

364 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Type uint16
Direction OUT
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors –

Operation RequestResults
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/Dcm
DspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutine
SignalType)} != VARIABLE_LENGTH) &&({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine/DcmDspRequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
DataIn_{Signal}
Type Dcm_RequestDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.SHORT-NAME)}Routine = {ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspRoutine.SHORT-NAME)}
DataIn_{Signal}
Type Dcm_RequestFlexibleInArrayData_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.SHORT-NAME)}Routine = {ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspRoutine.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_RequestDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
5

365 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors –

Operation RequestResults
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/Dcm
DspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutine
SignalType)} == VARIABLE_LENGTH) &&({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine/DcmDspRequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
DataIn_{Signal}
Type Dcm_RequestDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.SHORT-NAME)}Routine = {ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspRoutine.SHORT-NAME)}
DataIn_{Signal}
Type Dcm_StartFlexibleInArrayData_{Routine}_{Signal}Type
Direction IN
Comment –
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_RequestDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutine
Results/DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResults
OutSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataOut_{Signal}
Type Dcm_RequestFlexibleOutArrayData_{Routine}_{Signal}Type
Direction OUT
5

366 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutine
Results/DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResults
OutSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
currentDataLength
Type uint16
Direction OUT
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation RequestResultsConfirmation
Comment This operation indicates the transmission of a response to a RequestResultsRoutine request
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/Dcm
DspRequestRoutineResultsConfirmationEnabled)}==TRUE)
Parameters ConfirmationStatus
Type Dcm_ConfirmationStatusType
Direction IN
Comment Confirmation status of a RequestResultsRoutinerequest
Variation –
Possible Errors E_OK
E_NOT_OK

Operation Start
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH)
&&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.DcmDspRoutineSignalType)} != VARIABLE_
LENGTH)
DataIn_{Signal}
Type Dcm_StartDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
5

367 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_StartDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation Start
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH)
&&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.DcmDspRoutineSignalType)} == VARIABLE_
LENGTH)
DataIn_{Signal}
Type Dcm_StartDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
5

368 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Comment –
Variation –
DataOut_{Signal}
Type Dcm_StartDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)
DataOut_{Signal}
Type Dcm_StartFlexibleOutArrayData_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation –
currentDataLength
Type uint16
Direction OUT
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation Start
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.DcmDspRoutineSignalType)} == VARIABLE_
LENGTH) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.DcmDspRoutineSignalType)} != VARIABLE_
LENGTH)
DataIn_{Signal}
Type Dcm_StartDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
5

369 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
DataIn_{Signal}
Type Dcm_StartFlexibleInArrayData_{Routine}_{Signal}Type
Direction IN
Comment –
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_StartDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)
currentDataLength
Type uint16
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation Start
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.DcmDspRoutineSignalType)} == VARIABLE_
LENGTH) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.DcmDspRoutineSignalType)} == VARIABLE_
LENGTH)
DataIn_{Signal}
Type Dcm_StartDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
5

370 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/
DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDspRoutineSignal
Type)} != VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataIn_{Signal}
Type Dcm_StartFlexibleInArrayData_{Routine}_{Signal}Type
Direction IN
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/
DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDspRoutineSignal
Type)} == VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_StartDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/
DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.DcmDspRoutine
SignalType)} != VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataOut_{Signal}
Type Dcm_StartFlexibleOutArrayData_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/
DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.DcmDspRoutine
SignalType)} == VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
currentDataLength
Type uint16
Direction INOUT
5

371 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation StartConfirmation
Comment This operation indicates the transmission of a response to a StartRoutine request
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineConfirmationEnabled)}==TRUE
Parameters ConfirmationStatus
Type Dcm_ConfirmationStatusType
Direction IN
Comment Confirmation status of a StartRoutine request
Variation –
Possible Errors E_OK
E_NOT_OK

Operation Stop
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH)
&&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.DcmDspRoutineSignalType)} != VARIABLE_
LENGTH)
DataIn_{Signal}
Type Dcm_StopDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_StopDataOut_{Routine}_{Signal}Type
5

372 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Direction OUT
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation Stop
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH)
&&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.DcmDspRoutineSignalType)} == VARIABLE_
LENGTH)
DataIn_{Signal}
Type Dcm_StopDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_StopDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)
DataOut_{Signal}
Type Dcm_StopFlexibleOutArrayData_{Routine}_{Signal}Type
5

373 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Direction OUT
Comment –
Variation –
currentDataLength
Type uint16
Direction OUT
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation Stop
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
&&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.DcmDspRoutineSignalType)} != VARIABLE_
LENGTH)
DataIn_{Signal}
Type Dcm_StopDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataIn_{Signal}
Type Dcm_StopFlexibleInArrayData_{Routine}_{Signal}Type
Direction IN
Comment –
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_StopDataOut_{Routine}_{Signal}Type
Direction OUT
5

374 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)
currentDataLength
Type uint16
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation Stop
Comment –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
&&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.DcmDspRoutineSignalType)} == VARIABLE_
LENGTH)
DataIn_{Signal}
Type Dcm_StopDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/
DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDspRoutineSignal
Type)} != VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataIn_{Signal}
Type Dcm_StopFlexibleInArrayData_{Routine}_{Signal}Type
Direction IN
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/
DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDspRoutineSignal
Type)} == VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
5

375 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_StopDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/
DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.DcmDspRoutine
SignalType)} != VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataOut_{Signal}
Type Dcm_StopFlexibleOutArrayData_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/
DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.DcmDspRoutine
SignalType)} == VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
currentDataLength
Type uint16
Direction INOUT
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation StopConfirmation
Comment This operation indicates the transmission of a response to a StopRoutine request
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineConfirmationEnabled)}==TRUE)
Parameters ConfirmationStatus
5

376 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Type Dcm_ConfirmationStatusType
Direction IN
Comment Confirmation status of a StopRoutine request
Variation –
Possible Errors E_OK
E_NOT_OK

c()
From the point of view of the DCM, the operations have the following signatures:

8.8.3.6 RequestControlServices_{Tid}

The following interface allows the Dcm to provide OBD Service $08 (see
[SWS_Dcm_00419]).
Using the concepts of the SW-C template, the interface is defined as follows:
[SWS_Dcm_00691] d
Name RequestControlServices_{Tid}
Comment –
IsService true
Variation Tid = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestControl.SHORT-NAME)}
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed

Operation RequestControl
Comment –
Variation –
OutBuffer
Parameters
Type Dcm_RequestControlServicesOutArray_{Tid}Type
Direction OUT
Comment –
Variation Tid = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequest
Control.SHORT-NAME)}
InBuffer
Type Dcm_RequestControlServicesInArray_{Tid}Type
Direction IN
Comment –
Variation Tid = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequest
Control.SHORT-NAME)}
Possible Errors E_OK
E_NOT_OK

c()

377 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.3.7 CallbackDCMRequestServices

The following interface provides information on the status of the protocol commu-
nication and allows the Application to disallow a protocol (see [SWS_Dcm_00036],
[SWS_Dcm_00144], [SWS_Dcm_00145], [SWS_Dcm_00146]; [SWS_Dcm_00147],
[SWS_Dcm_00459]).
Using the concepts of the SW-C template, the interface is defined as follows:
[SWS_Dcm_00692] d
Name CallbackDCMRequestServices
Comment –
IsService true
Variation –
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
5 E_PROTOCOL_NOT_ conditions in application allows no further procession
ALLOWED of protocol

Operation StartProtocol
Comment –
Variation –
ProtocolType
Parameters
Type Dcm_ProtocolType
Direction IN
Comment –
Variation –
TesterSourceAddress
Type uint16
Direction IN
Comment –
Variation –
ConnectionId
Type uint16
Direction IN
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
E_PROTOCOL_NOT_ALLOWED

Operation StopProtocol
Comment –
Variation –
Parameters ProtocolType
5

378 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Type Dcm_ProtocolType
Direction IN
Comment –
Variation –
TesterSourceAddress
Type uint16
Direction IN
Comment –
Variation –
ConnectionId
Type uint16
Direction IN
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

c()

8.8.3.8 ServiceRequestNotification

The following interface indicates to the Application that a service is about to be ex-
ecuted and allows the Application to reject the execution of the service request (see
[SWS_Dcm_00218], [SWS_Dcm_00462], [SWS_Dcm_00463]).
Using the concepts of the SW-C template, the interface is defined as follows:
[SWS_Dcm_00694] d
Name ServiceRequestNotification
Comment –
IsService true
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceRequestManufacturerNotification)} !=
NULL)||({ecuc(Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceRequestSupplierNotification)} !=
NULL)
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
8 E_REQUEST_NOT_ no response will be sent
ACCEPTED

Operation Confirmation
Comment –
Variation –
Parameters SID
5

379 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Type uint8
Direction IN
Comment Value of service identifier
Variation –
ReqType
Type uint8
Direction IN
Comment Addressing type of the request(0=physical request, 1=functional request)
Variation –
ConnectionId
Type uint16
Direction IN
Comment Unique connection identifier
Variation –
ConfirmationStatus
Type Dcm_ConfirmationStatusType
Direction IN
Comment Confirmation of a successful transmission or a transmission error of a
diagnostic service.
Variation –
ProtocolType
Type Dcm_ProtocolType
Direction IN
Comment –
Variation –
TesterSourceAddress
Type uint16
Direction IN
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation Indication
Comment –
Variation –
SID
Type uint8
Direction IN
Comment Value of service identifier
Variation –
RequestData
Type Dcm_RequestDataArrayType
Direction IN
5

380 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Comment This parameter contains the complete request data (diagnostic buffer), except
the service ID
Variation –
DataSize
Type uint16
Direction IN
Comment This parameter defines how many bytes in the RequestData parameter are
valid
Variation –
ReqType
Type uint8
Direction IN
Comment Addressing type of the request(0=physical request, 1=functional request
Variation –
ConnectionId
Type uint16
Direction IN
Comment Unique connection identifier
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
ProtocolType
Type Dcm_ProtocolType
Direction IN
Comment –
Variation –
TesterSourceAddress
Type uint16
Direction IN
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
E_REQUEST_NOT_ACCEPTED

c()

8.8.3.9 UploadDownloadServices

[SWS_Dcm_91065] d

381 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name UploadDownloadServices
Comment –
IsService true
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspMemoryTransfer.DcmDspMemoryTransferUse
Port)} == TRUE)
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
10 DCM_E_PENDING Request is not yet finished. Further call(s) required
to finish.
12 DCM_E_FORCE_RCRRP application request the transmission of a response
Response Pending (NRC 0x78)

Operation ProcessRequestDownload
Comment Callout function.
DCM shall call this callout function to start a download process.
This service is needed for the implementation of UDS service RequestDownload.
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL
DCM_PENDING
DCM_CANCEL
Variation –
DataFormatIdentifier
Type uint8
Direction IN
Comment Bit 7 - 4: Compression Method
• 0x0: not compressed
• 0x1..F: vehicle-manufacturer-specific
Bit 3 - 0: Encrypting method
• 0x0: not encrypted
• 0x1..F: vehicle-manufacturer-specific
Variation –
MemoryIdentifier
Type uint8
Direction IN
Comment Identifier of the Memory Block, if the parameter is not used it shall be set to 0.
Variation –
MemoryAddress
Type uint32
Direction IN
Comment Starting address of server memory to which data is to be written
Variation –
MemorySize
5

382 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Type uint32
Direction IN
Comment Uncompressed memory size in bytes
Variation –
BlockLength
Type uint32
Direction INOUT
Comment Max. Number of bytes for one Dcm_WriteMemory
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ProcessRequestDownload returns value E_NOT_OK,
the DCM module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ProcessRequestTransferExit
Comment Callout function.
DCM shall call this callout function to terminate a download or upload process.
This callout is needed for the implementation of UDS service RequestTransferExit.
Variation –
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL
DCM_PENDING
DCM_CANCEL
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment see below
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ProcessRequestUpload
Comment Callout function.
DCM shall call this callout function to start an upload process.
This service is needed for the implementation of UDS service RequestUpload.
5

383 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL
DCM_PENDING
DCM_CANCEL
DCM_FORCE_RCRRP_OK
Variation –
DataFormatIdentifier
Type uint8
Direction IN
Comment Bit 7 - 4: Compression Method

• 0x0: not compressed

• 0x1..F: vehicle-manufacturer-specific

Bit 3 - 0: Encrypting method

• 0x0: not encrypted

• 0x1..F: vehicle-manufacturer-specific
Variation –
MemoryIdentifier
Type uint8
Direction IN
Comment Identifier of the Memory Block, if the parameter is not used it shall be set to 0.
Variation –
MemoryAddress
Type uint32
Direction IN
Comment Starting address of server memory from which data are to be copied
Variation –
MemorySize
Type uint32
Direction IN
Comment Uncompressed memory size in bytes
Variation –
BlockLength
Type uint32
Direction INOUT
Comment Max. Number of bytes for one Dcm_ReadMemory
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
5

384 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Direction OUT
Comment If the operation Dcm_ProcessRequestUpload returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ProcessTransferDataRead
Comment The ProcessTransferDataRead callout is used to request memory data identified by the
parameter memoryAddress and memorySize from the UDS request message.
This service is needed for the implementation of UDS services:
• ReadMemoryByAddress
• RequestUpload
• ReadDataByIdentifier (in case of Dynamical DID defined by memory address)
• TransferData
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL
DCM_PENDING
DCM_CANCEL
DCM_FORCE_RCRRP_OK
Variation –
MemoryIdentifier
Type uint8
Direction IN
Comment Identifier of the Memory Block (e.g. used if memory section distinguishing is
needed)
Note: If it’s not used this parameter shall be set to 0.
Variation –
MemoryAddress
Type uint32
Direction IN
Comment Starting address of server memory from which data is to be retrieved.
Variation –
MemorySize
Type uint32
Direction IN
Comment Number of bytes in the MemoryData
Variation –
MemoryData
Type Dcm_RequestDataArrayType
Direction OUT
5

385 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Comment Data read (Points to the diagnostic buffer in DCM)
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ReadMemory returns value DCM_READ_FAILED, the
Dcm module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation ProcessTransferDataWrite
Comment The ProcessTransferDataWrite callout is used to write memory data identified by the parameter
memoryAddress and memorySize. This service is needed for the implementation of UDS
services :
• WriteMemoryByAddress
• RequestDownload
• TransferData
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL
DCM_PENDING
DCM_CANCEL
DCM_FORCE_RCRRP_OK
Variation –
MemoryIdentifier
Type uint8
Direction IN
Comment Identifier of the Memory Block (e.g. used by WriteDataByIdentifier service).
Note: If it’s not used this parameter shall be set to 0.
Variation –
MemoryAddress
Type uint32
Direction IN
Comment Starting address of server memory in which data is to be copied.
Note: If it’s not used (e.g. if the data is compressed) this parameter shall be set
to 0.
Variation –
MemorySize
Type uint32
Direction IN
5

386 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Comment Number of bytes in MemoryData
Variation –
MemoryData
Type Dcm_RequestDataArrayType
Direction IN
Comment Data to write (Points to the diagnostic buffer in DCM)
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_WriteMemory returns value DCM_WRITE_FAILED, the
Dcm module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

c()

8.8.3.10 RequestFileTransfer

[SWS_Dcm_91086] d
Name RequestFileTransfer
Comment –
IsService true
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer/DcmRequestFileTransfer
UsePort)} == TRUE)
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
10 DCM_E_PENDING Request is not yet finished. Further call(s) required
to finish.
12 DCM_E_FORCE_RCRRP application request the transmission of a response
Response Pending (NRC 0x78)

Operation ProcessRequestAddFile
Comment Callout function.
DCM shall call this function to start a RequestFileTransfer process with modeOfOperation equal
to 0x01 (AddFile).
Variation –
OpStatus
Type Dcm_OpStatusType
5

387 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Direction IN
Comment DCM_INITIAL: All In-parameters are valid.
DCM_PENDING: All In-parameters are set to 0x00.
DCM_CANCEL: All In-parameters are set to 0x00.
DCM_FORCE_RCRRP_OK: All In-parameters are set to 0x00.
Variation –
filePathAndNameLength
Type uint16
Direction IN
Comment Defines the length in bytes for the parameter filePathAndName.
Variation –
filePathAndName
Type const Dcm_FileAndDirNameType
Direction IN
Comment Defines the file system location of the server where the file which shall be
added, deleted, replaced or read from depending on the parameter modeOf
Operation parameter. In addition this parameter includes the file name of the
file which shall be added, deleted, replaced or read as part of the file path.
Variation –
dataFormatIdentifier
Type uint8
Direction IN
Comment This data-parameter is a one byte value with each nibble encoded separately.
The high nibble specifies the "compressionMethod", and the low nibble
specifies the "encryptingMethod". The value 0x00 specifies that neither
compressionMethod nor encryptingMethod is used. Values other than 0x00
are vehicle manufacturer specific.
Variation –
fileSizeUncompressed
Type uint64
Direction IN
Comment Defines the size of the uncompressed file to be download in bytes.
Variation –
fileSizeCompressed
Type uint64
Direction IN
Comment Defines the size of the compressed file to be downloaded in bytes.
Variation –
maxNumberOfBlockLength
Type uint64
Direction OUT
Comment Max number of bytes to be included in each TransferData request excluding
the SID and the blockSequenceCounter.
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
5

388 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Comment If the operation Dcm_ProcessRequestAddFile returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation ProcessRequestDeleteFile
Comment Callout function.
DCM shall call this function to start a RequestFileTransfer process with modeOfOperation equal
to 0x02 (DeleteFile).
Variation –
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL: All In-parameters are valid.
DCM_PENDING: All In-parameters are set to 0x00.
DCM_CANCEL: All In-parameters are set to 0x00.
DCM_FORCE_RCRRP_OK: All In-parameters are set to 0x00.
Variation –
filePathAndNameLength
Type uint16
Direction IN
Comment Defines the length in bytes for the parameter filePathAndName.
Variation –
filePathAndName
Type const Dcm_FileAndDirNameType
Direction IN
Comment Defines the file system location of the server where the file which shall be
added, deleted, replaced or read from depending on the parameter modeOf
Operation parameter. In addition this parameter includes the file name of the
file which shall be added, deleted, replaced or read as part of the file path.
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ProcessRequestDeleteFile returns value E_NOT_OK,
the DCM module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

389 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Operation ProcessRequestReadDir
Comment Callout function.
DCM shall call this function to start a RequestFileTransfer process with modeOfOperation equal
to 0x05 (ReadDir).
Variation –
OpStatus
Parameters Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL: All In-parameters are valid.
DCM_PENDING: All In-parameters are set to 0x00.
DCM_CANCEL: All In-parameters are set to 0x00.
DCM_FORCE_RCRRP_OK: All In-parameters are set to 0x00.
Variation –
filePathAndNameLength
Type uint16
Direction IN
Comment Defines the length in bytes for the parameter filePathAndName.
Variation –
filePathAndName
Type const Dcm_FileAndDirNameType
Direction IN
Comment Defines the file system location of the server where the file which shall be
added, deleted, replaced or read from depending on the parameter modeOf
Operation parameter. In addition this parameter includes the file name of the
file which shall be added, deleted, replaced or read as part of the file path.
Variation –
dirInfoLength
Type uint64
Direction OUT
Comment Defines the size of directory information to be uploaded in bytes.
Variation –
maxNumberOfBlockLength
Type uint64
Direction OUT
Comment Max number of bytes to be included in each TransferData request excluding
the SID and the blockSequenceCounter.
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ProcessRequestReadDir returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

390 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Operation ProcessRequestReadFile
Comment Callout function.
DCM shall call this function to start a RequestFileTransfer process with modeOfOperation equal
to 0x04 (ReadFile).
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL: All In-parameters are valid.
DCM_PENDING: All In-parameters are set to 0x00.
DCM_CANCEL: All In-parameters are set to 0x00.
DCM_FORCE_RCRRP_OK: All In-parameters are set to 0x00.
Variation –
filePathAndNameLength
Type uint16
Direction IN
Comment Defines the length in bytes for the parameter filePathAndName.
Variation –
filePathAndName
Type const Dcm_FileAndDirNameType
Direction IN
Comment Defines the file system location of the server where the file which shall be
added, deleted, replaced or read from depending on the parameter modeOf
Operation parameter. In addition this parameter includes the file name of the
file which shall be added, deleted, replaced or read as part of the file path.
Variation –
dataFormatIdentifier
Type uint8
Direction IN
Comment This data-parameter is a one byte value with each nibble encoded separately.
The high nibble specifies the "compressionMethod", and the low nibble
specifies the "encryptingMethod". The value 0x00 specifies that neither
compressionMethod nor encryptingMethod is used. Values other than 0x00
are vehicle manufacturer specific.
Variation –
fileSizeUncompressed
Type uint64
Direction OUT
Comment Defines the size of the uncompressed file to be uploaded in bytes.
Variation –
fileSizeCompressed
Type uint64
Direction OUT
Comment Defines the size of the compressed file to be uploaded in bytes.
Variation –
maxNumberOfBlockLength
Type uint64
5

391 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Direction OUT
Comment Max number of bytes to be included in each TransferData response excluding
the SID and the blockSequenceCounter.
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ProcessRequestReadFile returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation ProcessRequestReplaceFile
Comment Callout function.
DCM shall call this function to start a RequestFileTransfer process with modeOfOperation equal
to 0x03 (ReplaceFile).
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL: All In-parameters are valid.
DCM_PENDING: All In-parameters are set to 0x00.
DCM_CANCEL: All In-parameters are set to 0x00.
DCM_FORCE_RCRRP_OK: All In-parameters are set to 0x00.
Variation –
filePathAndNameLength
Type uint16
Direction IN
Comment Defines the length in bytes for the parameter filePathAndName.
Variation –
filePathAndName
Type const Dcm_FileAndDirNameType
Direction IN
Comment Defines the file system location of the server where the file which shall be
added, deleted, replaced or read from depending on the parameter modeOf
Operation parameter. In addition this parameter includes the file name of the
file which shall be added, deleted, replaced or read as part of the file path.
Variation –
dataFormatIdentifier
Type uint8
Direction IN
5

392 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Comment This data-parameter is a one byte value with each nibble encoded separately.
The high nibble specifies the "compressionMethod", and the low nibble
specifies the "encryptingMethod". The value 0x00 specifies that neither
compressionMethod nor encryptingMethod is used. Values other than 0x00
are vehicle manufacturer specific.
Variation –
fileSizeUncompressed
Type uint64
Direction IN
Comment Defines the size of the uncompressed file to be download in bytes.
Variation –
fileSizeCompressed
Type uint64
Direction IN
Comment Defines the size of the compressed file to be downloaded in bytes.
Variation –
maxNumberOfBlockLength
Type uint64
Direction OUT
Comment Max number of bytes to be included in each TransferData request excluding
the SID and the blockSequenceCounter.
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ProcessRequestReplaceFile returns value E_NOT_OK,
the DCM module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation ReadFileOrDir
Comment Callout function.
DCM shall call this function when data shall be sent as a response to UDS service TransferData
if there’s an ongoing RequestFileTransfer process started with 0x04 (ReadFile) or 0x05 (Read
Dir).
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL: All In-parameters are valid.
DCM_PENDING: All In-parameters are set to 0x00.
DCM_CANCEL: All In-parameters are set to 0x00.
DCM_FORCE_RCRRP_OK: All In-parameters are set to 0x00.
5

393 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Variation –
DataLength
Type uint64
Direction INOUT
Comment As in, the parameter defines the maximum block length to be used, i.e. the
value of maxNumberOfBlockLength sent to the client in the response of
RequestFileTransfer.
As out, the parameter defines the actual length in bytes for the parameter
Data. The value shall not exceed, but might be less, the value provided as in
parameter.
Variation –
Data
Type Dcm_ResponseDataArrayType
Direction IN
Comment Pointer to the data to be written.
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ReadFileOrDir returns value E_NOT_OK, the DCM
module shall send a negative response with NRC code equal to the parameter
ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation WriteFile
Comment Callout function.
DCM shall call this function when data is received using UDS service TransferData if there’s an
ongoing RequestFileTransfer process started with 0x01 (AddFile) or 0x03 (ReplaceFile).
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL: All In-parameters are valid.
DCM_PENDING: All In-parameters are set to 0x00.
DCM_CANCEL: All In-parameters are set to 0x00.
DCM_FORCE_RCRRP_OK: All In-parameters are set to 0x00.
Variation –
DataLength
Type uint64
Direction IN
Comment Defines the length in bytes for the parameter Data. The value will not exceed,
but might be less, compared to the value of maxNumberOfBlockLength return
in Dcm_ProcessRequestFileTransfer.
Variation –
5

394 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Data
Type Dcm_RequestDataArrayType
Direction IN
Comment Pointer to the data to be written.
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_WriteFile returns value E_NOT_OK, the DCM module
shall send a negative response with NRC code equal to the parameter Error
Code parameter value.
Variation –
Possible Errors –

c()

8.8.3.11 DCMServices

[SWS_Dcm_00698] d
Name DCMServices
Comment –
IsService true
Variation –
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed

Operation GetActiveProtocol
Comment –
Variation –
ActiveProtocolType
Type Dcm_ProtocolType
Direction OUT
Comment –
Variation –
ConnectionId
Type uint16
Direction OUT
Comment –
Variation –
TesterSourceAddress
Type uint16
Direction OUT
5

395 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Comment –
Variation –
Possible Errors E_OK

Operation GetSecurityLevel
Comment –
Variation –
Parameters SecLevel
Type Dcm_SecLevelType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation GetSesCtrlType
Comment –
Variation –
Parameters SesCtrlType
Type Dcm_SesCtrlType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ResetToDefaultSession
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation SetActiveDiagnostic
Comment Allows to activate and deactivate the call of ComM_DCM_ActiveDiagnostic() function.
Variation –
Parameters active
Type boolean
Direction IN
Comment If false Dcm shall not call ComM_DCM_ActiveDiagnostic(). If true Dcm will call
ComM_DCM_ActiveDiagnostic().
Variation –
Possible Errors E_OK

c()

396 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.3.12 DCM_Roe

The RoeEventId shall be a Portdefined argument value.

[SWS_Dcm_00699] d
Name DCM_Roe
Comment –
IsService true
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoe/DcmDspRoeEvent)}
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed

Operation TriggerOnEvent
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

c()

8.8.3.13 Authentication

[SWS_Dcm_91072] d
Name Authentication
Comment –
IsService true
Variation –
Possible Errors 0 E_OK Operation successful

Operation SetDeauthenticatedRole
Comment Sets a new role used in deauthenticated state for that connection. The set role is valid until the
connection switches into authenticated state or the ECU is reset.
Variation –
Parameters deauthenticatedRole
Type Dcm_AuthenticationRoleType
Direction IN
Comment New deauthenticated role that is assigned to that connection.
Variation –
Possible Errors E_OK

c()

397 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.4 NvDataInterface

8.8.4.1 DataServices_{DID}

[SWS_Dcm_91061] d
Name DataServices_{DID}
Comment –
IsService false
Variation ( {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_ATOMIC_
NV_DATA_INTERFACE)
DID = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)}
Data Elements data
Type {DID}_Struct_DataType
Variation DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})

c(RS_Diag_04218)

8.8.5 Ports

This section formally specifies the corresponding AUTOSAR Service using the con-
cepts of the Software-Component-Template. The following definition can be generated
completely out of the configuration of the Dcm, which defines the exact ports that are
present and their names.
Naming of the port : The prefix of the port name is fixed and defined herafter (e.g.
DataServices_). The name behind the prefix corresponds to the name of the associ-
ated container in the ECU configuration and can be freely defined during the configu-
ration step. e.g. : for a DcmDspData container called Speed the port name would be
DataServices_Speed
1 ServiceSwComponentType Dcm {
2

3 //the presence and name of this port is configuration-independent

4 ProvidePort DCMServices DCMServices;
5
6 //see configuration parameter DcmDspSecurityRow
7 RequirePort SecurityAccess_\{SecurityLevel\} SecurityAccess_\{
SecurityLevel\};
8 ...
9
10
11 //see configuration parameter DcmDspData
12 RequirePort DataServices_\{Data\} DataServices_\{Data\};
13 ProvidePort DataServices_\{Data\} DataServices_\{Data\}; // Only if
the data can be written and DcmDspDataUsePort is set to
USE_DATA_SENDER_RECEIVER or to USE_DATA_SENDER_RECEIVER_AS_SERVICE
14 ...
15
16

17 //see configuration parameter DcmDspVehInfoData

398 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

18 RequirePort InfotypeServices_{VehInfoData}
19 InfotypeServices_{VehInfoData}
20 ...
21
22
23 //see configuration parameter DcmDspRoutine
24 RequirePort RoutineServices_{RoutineName}
25 RoutineServices_{RoutineName};
26 ...
27
28 //see configuration parameter DcmDspRequestControl
29 RequirePort RequestControlServices_\{Tid\}
30 RequestControlServices_\{Tid\};
31 ...
32
33 //see configuration parameter DcmDslCallbackDCMRequestService
34 RequirePort CallbackDCMRequestServices
35 CallbackDCMRequestServices_\_SWC>;
36 ...
37
38 //see configuration parameter
DcmDsdServiceRequestManufacturerNotication
39 RequirePort ServiceRequestNotification
40 ServiceRequestManufacturerNotification_{Name};
41 ...
42
43 //see configuration parameter DcmDsdServiceRequestSupplierNotication
44 RequirePort ServiceRequestNotification
45 ServiceRequestSupplierNotification_\_SWC>;
46 ...
47
48 //Note: When service 0x19 subfunctions 0x14 is used (call to //
Dem_GetNextFilteredDTCAndFDC), the following is defined:
49 //Non-DEM-internal calculated fault detection counters are typically
50 //requested from SW-Cs through the RTE. To indicate an equivalent call-
tree //for these runables, a work-around is used: The Dcm main
function //specifies a trigger to the DEM interface GeneralEvtInfo
(operation //GetFaultDetectionCounter), which triggers the
according ehavior (refer to //RunnableEntity
GetFaultDetectionCounter, chapter "Service Interface //
DiagnosticInfo & General" in DEM SWS)."
51 RequirePort Dem/CallbackGetFaultDetectCounter CBFaultDetectCtrDummy
52 (The client-server interface can be used from the DEM.)
53
54 RunnableEntity MainFunction
55 symbol \ARApiRef{Dcm_MainFunction}"
56 canbeInvokedConcurrently = FALSE
57 SSCP = port CBFaultDetectCtrDummy,
GetFaultDetectionCounter
58
59 Connector from CBFaultDetectCtrDummy to Dem/GeneralEvtInfo
60 }

399 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.5.1 Dcm_CallbackDCMRequestServices_{Name}

[SWS_Dcm_01033] d
Name CallbackDCMRequestServices_{Name}
Kind RequiredPort Interface CallbackDCMRequestServices
Description –
Variation Name = {ecuc(Dcm/DcmConfigSet/DcmDsl/DcmDslCallbackDCMRequestService.SHORT-NAME)}

c()

8.8.5.2 DataServices_DIDRange_{Range}

[SWS_Dcm_01034] d
Name DataServices_DIDRange_{Range}
Kind RequiredPort Interface DataServices_DIDRange_{Range}
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange.DcmDspDidRangeUsePort)} == TRUE
Range = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange.SHORT-NAME)})

c()

8.8.5.3 DataServices_{DID}

[SWS_Dcm_91058] d
Name DataServices_{DID}
Kind ProvidedPort Interface –
Description –
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_
SENDER_RECEIVER_INTERFACE ) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidUsePort)} == (USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE )
||({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_NV_
DATA_INTERFACE)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->
DcmDspDidInfo/DcmDspDidWrite)} != NULL) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Did/DcmDspDidInfoRef-> DcmDspDidInfo/DcmDspDidRead)} == NULL) ||({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDspDidInfo/DcmDspDidControl)} !=NULL))
DID = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)}

c(RS_Diag_04218)
[SWS_Dcm_91060] d

400 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DataServices_{DID}
Kind Provided Interface –
RequiredPort
Description –
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_
SENDER_RECEIVER_INTERFACE ) ||({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidUsePort)} == (USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE )
||({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_NV_
DATA_INTERFACE)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidWrite)} != NULL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidRead)} != NULL))
DID = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)}

c(RS_Diag_04218)
[SWS_Dcm_91059] d
Name DataServices_{DID}
Kind RequiredPort Interface –
Description –
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_
SENDER_RECEIVER_INTERFACE ) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidUsePort)} == (USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE )
||({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_NV_
DATA_INTERFACE)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidWrite)} == NULL) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidRead)} != NULL) ||({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl)}
!=NULL))
DID = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)}

c(RS_Diag_04218)

8.8.5.4 DataServices_{Data}

[SWS_Dcm_01035] d
Name DataServices_{Data}
Kind RequiredPort Interface –
Description –
Variation ( {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/Dcm
DspPidDataUsePort)} ==(USE_DATA_SYNCH_CLIENT_SERVER ||USE_DATA_SENDER_
RECEIVER ||USE_DATA_SENDER_RECEIVER_AS_SERVICE))
Data = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)} || {ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.SHORT-NAME)}

c()
[SWS_Dcm_01310] d

401 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DataServices_{Data}
Kind RequiredPort Interface –
Description –
Variation ((( {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_DATA_
ELEMENT_SPECIFIC_INTERFACES)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/
DcmDspDataUsePort)} == (USE_DATA_SENDER_RECEIVER ||USE_DATA_SENDER_
RECEIVER_AS_SERVICE))) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef-> DcmDspDidInfo/DcmDspDidWrite)} == NULL) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspDid/DcmDspDidInfoRef-> DcmDspDidInfo/DcmDspDidRead)} != NULL)))
Data = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}

c()
[SWS_Dcm_01031] d
Name DataServices_{Data}
Kind ProvidedPort Interface –
Description –
Variation ((( {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_DATA_
ELEMENT_SPECIFIC_INTERFACES)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/
DcmDspDataUsePort)} == (USE_DATA_SENDER_RECEIVER ||USE_DATA_SENDER_
RECEIVER_AS_SERVICE))) &&({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref-> DcmDspDidInfo/DcmDspDidWrite)} != NULL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDid/DcmDspDidInfoRef-> DcmDspDidInfo/DcmDspDidRead)} == NULL)
Data = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}

c()
[SWS_Dcm_01311] d
Name DataServices_{Data}
Kind Provided Interface DataServices_{Data}
RequiredPort
Description –
Variation ((( {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_DATA_
ELEMENT_SPECIFIC_INTERFACES)) &&({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/Dcm
DspDataUsePort)} == (USE_DATA_SENDER_RECEIVER ||USE_DATA_SENDER_RECEIVER_
AS_SERVICE))) &&({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> Dcm
DspDidInfo/DcmDspDidWrite)} != NULL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/
DcmDspDidInfoRef-> DcmDspDidInfo/DcmDspDidRead)} != NULL)
Data = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}

c()

8.8.5.5 IOControlRequest_{DID}

[SWS_Dcm_01312] d

402 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name IOControlRequest_{DID}
Kind Provided Interface IOControlRequest_{DID}
RequiredPort
Description –
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_
SENDER_RECEIVER_INTERFACE || USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_
SERVICE))) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDsp
DidInfo/DcmDspDidControl)} != NULL)
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})

c()

8.8.5.6 IOControlResponse_{DID}

[SWS_Dcm_01313] d
Name IOControlResponse_{DID}
Kind RequiredPort Interface IOControlResponse_{DID}
Description –
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_
SENDER_RECEIVER_INTERFACE || USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_
SERVICE))) &&({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDsp
DidInfo/DcmDspDidControl)} != NULL)
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})

c(RS_Diag_04218)

8.8.5.7 DCM_Roe_{RoeName}

[SWS_Dcm_01032] d
Name DCM_Roe_{RoeName}
Kind ProvidedPort Interface DCM_Roe
Description –
Port Defined Type uint8
Argument Value(s)
Value {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoe/DcmDspRoeEvent/DcmDsp
RoeEventId.value)}
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoe/DcmDspRoeEvent)}
RoeName = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoe/DcmDspRoeEvent.SHORT-NAME)}

c()

8.8.5.8 DCMServices

[SWS_Dcm_01030] d

403 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DCMServices
Kind ProvidedPort Interface DCMServices
Description –
Variation –

c()

8.8.5.9 InfotypeServices_{VehInfoData}

[SWS_Dcm_01037] d
Name InfotypeServices_{VehInfoData}
Kind RequiredPort Interface InfotypeServices_{VehInfoData}
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfoData/DcmDspVehInfoData
UsePort)}==TRUE
VehInfoData = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfo
Data.SHORT-NAME)}

c()

8.8.5.10 RequestControlServices_{Tid}

[SWS_Dcm_01038] d
Name RequestControlServices_{Tid}
Kind RequiredPort Interface RequestControlServices_{Tid}
Description –
Variation Tid = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestControl.SHORT-NAME)}

c()

8.8.5.11 RequestFileTransfer

[SWS_Dcm_91143] d
Name RequestFileTransfer
Kind RequiredPort Interface RequestFileTransfer
Description –
5

404 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer/DcmRequestFileTransferUse
Port)} == TRUE)

c()

8.8.5.12 ServiceRequestManufacturerNotification_{Name}

[SWS_Dcm_01039] d
Name ServiceRequestManufacturerNotification_{Name}
Kind RequiredPort Interface ServiceRequestNotification
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceRequestManufacturerNotification)} != NULL)
Name = {ecuc(Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceRequestManufacturer
Notification.SHORT-NAME)}

c()

8.8.5.13 ServiceRequestSupplierNotification_{Name}

[SWS_Dcm_01042] d
Name ServiceRequestSupplierNotification_{Name}
Kind RequiredPort Interface ServiceRequestNotification
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceRequestSupplierNotification)} != NULL)
Name = {ecuc(Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceRequestSupplier
Notification.SHORT-NAME)}

c()

8.8.5.14 RoutineServices_{RoutineName}

[SWS_Dcm_01040] d
Name RoutineServices_{RoutineName}
Kind RequiredPort Interface RoutineServices_{RoutineName}
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.DcmDspRoutineUsePort)} == TRUE
RoutineName = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}

c()

405 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.5.15 SecurityAccess_{SecurityLevel}

[SWS_Dcm_01041] d
Name SecurityAccess_{SecurityLevel}
Kind RequiredPort Interface SecurityAccess_{SecurityLevel}
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurityUse
Port)} == USE_ASYNCH_CLIENT_SERVER
SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurity
Row.SHORT-NAME)}

c()

8.8.5.16 Dcm_DiagnosticSessionControlModeSwitchInterface

[SWS_Dcm_91033] d
Name DiagnosticSessionControlModeSwitchInterface
Kind ProvidedPort Interface Dcm_DiagnosticSessionControlModeSwitchInterface
Description A ModeSwitchInterface PPortPrototype used to notify SW-Cs about the current Diagnostic Session
Variation –

c()

8.8.5.17 Dcm_EcuResetModeSwitchInterface

[SWS_Dcm_91034] d
Name EcuResetModeSwitchInterface
Kind ProvidedPort Interface Dcm_EcuResetModeSwitchInterface
Description A ModeSwitchInterface PPortPrototype used to notify SW-Cs about an upcoming ECU Reset and
its type
Variation –

c()

8.8.5.18 Dcm_ModeRapidPowerShutDownModeSwitchInterface

[SWS_Dcm_91035] d

406 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name ModeRapidPowerShutDownModeSwitchInterface
Kind ProvidedPort Interface Dcm_ModeRapidPowerShutDownModeSwitchInterface
Description A ModeSwitchInterface PPortPrototype used to notify SW-Cs about the rapid power shut down
mode
Variation –

c()

8.8.5.19 Dcm_CommunicationControlModeSwitchInterface_{ComMChannel-
Name}

[SWS_Dcm_91036] d
Name CommunicationControlModeSwitchInterface_{ComMChannelName}
Kind ProvidedPort Interface CommunicationControlModeSwitchInterface_{ComM
ChannelName}
Description A ModeSwitchInterface PPortPrototype used to notify SW-Cs about the communication control of
the indicated ComM channel
Variation ComMChannelName = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspComControl/DcmDspCom
ControlAllChannel/DcmDspAllComMChannelRef->ComMChannel.SHORT-NAME)} or {ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspComControl/DcmDspComControlSpecificChannel/DcmDsp
SpecificComMChannelRef->ComMChannel.SHORT-NAME)}

c()

8.8.5.20 Dcm_ControlDTCSettingModeSwitchInterface

[SWS_Dcm_91037] d
Name ControlDTCSettingModeSwitchInterface
Kind ProvidedPort Interface Dcm_ControlDTCSettingModeSwitchInterface
Description A ModeSwitchInterface PPortPrototype used to notify SW-Cs about the DTC Setting mode
Variation –

c()

8.8.5.21 Dcm_ResponseOnEventModeSwitchInterface_{RoeEventID}

[SWS_Dcm_91038] d

407 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name ResponseOnEventModeSwitchInterface_{RoeEventID}
Kind ProvidedPort Interface ResponseOnEvent_{RoeEventID}
Description A ModeSwitchInterface PPortPrototype used to notify SW-Cs about the mode of the indicated
Response On Event
Variation RoeEventID = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoe/DcmDspRoe
Event.SHORT-NAME)}

c()

8.8.5.22 Dcm_SecurityAccessModeSwitchInterface

[SWS_Dcm_91039] d
Name SecurityAccessModeSwitchInterface
Kind ProvidedPort Interface Dcm_SecurityAccessModeSwitchInterface
Description A ModeSwitchInterface PPortPrototype used to notify SW-Cs about the current Security Level
Variation –

c()

8.8.5.23 Dcm_UploadDownloadServices

[SWS_Dcm_91084] d
Name UploadDownloadServices
Kind RequiredPort Interface UploadDownloadServices
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspMemoryTransfer.DcmDspMemoryTransferUsePort)}
== TRUE)

c()

8.8.5.24 Dcm_Authentication_{Connection}

[SWS_Dcm_91073] d

408 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name Authentication_{Connection}
Kind RequiredPort Interface Authentication
Description –
Port Defined Type uint16
Argument Value(s)
Value {ecuc(Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/
DcmDslConnection/DcmDslMainConnection.DcmDslProtocolRxConnectionId
)}
Variation Connection = { Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDsl
Connection/DcmDslMainConnection.Short-Name)}

c()

8.8.6 ModeDeclarationGroups

8.8.6.1 DcmDiagnosticSessionControl

[SWS_Dcm_91019] d
Name DcmDiagnosticSessionControl
Kind ModeDeclarationGroup
Category EXPLICIT_ORDER
Initial mode DCM_DEFAULT_SESSION
On transition value 255
Modes DCM_DEFAULT_SESSION 0
DCM_PROGRAMMING_SESSION 1
DCM_EXTENDED_DIAGNOSTIC_SESSION 2
DCM_SAFETY_SYSTEM_DIAGNOSTIC_SESSION 3
Description ModeDeclarationGroup representing the different diagnostic sessions
Further modes to be added: {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSession/
DcmDspSessionRow.SHORT-NAME)}

c()
Note: According [SWS_Dcm_CONSTR_6001] there are standardized mode dec-
laration which are part of the standardized AUTOSAR interface. Note: Refer
[ecuc_sws_2108] defining the symbolic name prefix

8.8.6.2 DcmEcuReset

[SWS_Dcm_91021] d

409 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmEcuReset
Kind ModeDeclarationGroup
Category EXPLICIT_ORDER
Initial mode DCM_NONE
On transition value 255
Modes DCM_NONE 0
DCM_HARD 1
DCM_KEYONOFF 2
DCM_SOFT 3
DCM_JUMPTOBOOTLOADER 4
DCM_JUMPTOSYSSUPPLIERBOOTLOADER 5
DCM_EXECUTE 6
Description ModeDeclarationGroup representing the different ECU reset types

c()

8.8.6.3 DcmModeRapidPowerShutDown

[SWS_Dcm_91023] d
Name DcmModeRapidPowerShutDown
Kind ModeDeclarationGroup
Category EXPLICIT_ORDER
Initial mode DCM_ENABLE_RAPIDPOWERSHUTDOWN
On transition value 255
Modes DCM_ENABLE_RAPIDPOWERSHUTDOWN 0
DCM_DISABLE_RAPIDPOWERSHUTDOWN 1
Description ModeDeclarationGroup representing the enable/disable state of rapid power
shutdown

c()

8.8.6.4 DcmCommunicationControl

[SWS_Dcm_91025] d
Name DcmCommunicationControl
Kind ModeDeclarationGroup
Category EXPLICIT_ORDER
Initial mode DCM_ENABLE_RX_TX_NORM_NM
On transition value 255
5

410 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
DCM_ENABLE_RX_TX_NORM 0
Modes
DCM_ENABLE_RX_DISABLE_TX_NORM 1
DCM_DISABLE_RX_ENABLE_TX_NORM 2
DCM_DISABLE_RX_TX_NORMAL 3
DCM_ENABLE_RX_TX_NM 4
DCM_ENABLE_RX_DISABLE_TX_NM 5
DCM_DISABLE_RX_ENABLE_TX_NM 6
DCM_DISABLE_RX_TX_NM 7
DCM_ENABLE_RX_TX_NORM_NM 8
DCM_ENABLE_RX_DISABLE_TX_NORM_NM 9
DCM_DISABLE_RX_ENABLE_TX_NORM_NM 10
DCM_DISABLE_RX_TX_NORM_NM 11
Description ModeDeclarationGroup representing the different communication control states

c()

8.8.6.5 DcmControlDTCSetting

[SWS_Dcm_91027] d
Name DcmControlDTCSetting
Kind ModeDeclarationGroup
Category EXPLICIT_ORDER
Initial mode DCM_ENABLEDTCSETTING
On transition value 255
Modes DCM_ENABLEDTCSETTING 0
DCM_DISABLEDTCSETTING 1
Description ModeDeclarationGroup representing the enable/disable state for DTC storage

c()

8.8.6.6 DcmResponseOnEvent

[SWS_Dcm_91029] d
Name DcmResponseOnEvent
Kind ModeDeclarationGroup
Category EXPLICIT_ORDER
Initial mode DCM_EVENT_CLEARED
On transition value 255
5

411 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Modes DCM_EVENT_STARTED 0
DCM_EVENT_STOPPED 1
DCM_EVENT_CLEARED 2
Description ModeDeclarationGroup representing the state of a Response On Event

c()

8.8.6.7 DcmSecurityAccess

[SWS_Dcm_91031] d
Name DcmSecurityAccess
Kind ModeDeclarationGroup
Category EXPLICIT_ORDER
Initial mode DCM_SEC_LEV_LOCKED
On transition value 255
Modes DCM_SEC_LEV_LOCKED 0
Description ModeDeclarationGroup representing the different diagnostic security levels
Further modes to be added: {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Security/DcmDspSecurityRow.SHORT-NAME)}

c()

8.8.6.8 DcmAuthenticationState

[SWS_Dcm_91067] d
Name DcmAuthenticationState_{Connection}
Kind ModeDeclarationGroup
Category EXPLICIT_ORDER
Initial mode DCM_DEAUTHENTICATED
On transition value 255
Modes DCM_DEAUTHENTICATED 0
DCM_AUTHENTICATED 1
Description Representing the authentication state of a diagnostic connection.

c()

412 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

8.8.7 Mode-Switch-Interfaces

8.8.7.1 Dcm_DiagnosticSessionControlModeSwitchInterface

[SWS_Dcm_91020] d
Name Dcm_DiagnosticSessionControlModeSwitchInterface
Comment A SW-C that wants to get informed about the current Diagnostic Session requires the Mode
SwitchInterface Dcm_DiagnosticSessionControlModeSwitchInterface
IsService true
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSession/DcmDspSessionRow.SHORT-NAME)}
ModeGroup diagnosticSession DcmDiagnosticSessionControl

c()

8.8.7.2 Dcm_EcuResetModeSwitchInterface

[SWS_Dcm_91022] d
Name Dcm_EcuResetModeSwitchInterface
Comment A SW-C that wants to get informed about an upcoming ECU Reset requires the ModeSwitch
Interface Dcm_EcuResetModeSwitchInterface
IsService true
Variation –
ModeGroup ecuReset DcmEcuReset

c()

8.8.7.3 Dcm_ModeRapidPowerShutDownModeSwitchInterface

[SWS_Dcm_91024] d
Name Dcm_ModeRapidPowerShutDownModeSwitchInterface
Comment A SW-C that wants to get informed about the rapid power shut down mode requires the Mode
SwitchInterface Dcm_ModeRapidPowerShutDownModeSwitchInterface
IsService true
Variation –
ModeGroup modeRapidPowerShutDown DcmModeRapidPowerShutDown

c()

8.8.7.4 Dcm_CommunicationControlModeSwitchInterface

[SWS_Dcm_91026] d

413 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name CommunicationControlModeSwitchInterface_{ComMChannelName}
Comment A SW-C that wants to get informed about the communication control of a ComM channel
requires the ModeSwitchInterface Dcm_CommunicationControlModeSwitchInterface
IsService true
Variation ComMChannelName = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspComControl/DcmDspCom
ControlAllChannel/DcmDspAllComMChannelRef->ComMChannel.SHORT-NAME)} ||
{ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspComControl/DcmDspComControlSpecificChannel/
DcmDspSpecificComMChannelRef->
ModeGroup communicationControl DcmCommunicationControl

c()

8.8.7.5 Dcm_ControlDTCSettingModeSwitchInterface

[SWS_Dcm_91028] d
Name Dcm_ControlDTCSettingModeSwitchInterface
Comment A SW-C that wants to get informed about the DTC Setting mode requires the ModeSwitch
Interface Dcm_ControlDTCSettingModeSwitchInterface
IsService true
Variation –
ModeGroup controlDTCSetting DcmControlDTCSetting

c()

8.8.7.6 Dcm_ResponseOnEventModeSwitchInterface

[SWS_Dcm_91030] d
Name ResponseOnEvent_{RoeEventID}
Comment A SW-C that wants to get informed about a Response On Event mode requires the ModeSwitch
Interface Dcm_ResponseOnEventModeSwitchInterface
IsService true
Variation RoeEventID = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoe/DcmDspRoe
Event.SHORT-NAME)}
ModeGroup responseOnEvent DcmResponseOnEvent

c()

8.8.7.7 Dcm_SecurityAccessModeSwitchInterface

[SWS_Dcm_91032] d

414 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name Dcm_SecurityAccessModeSwitchInterface
Comment A SW-C that wants to get informed about the current Security Level requires the ModeSwitch
Interface Dcm_SecurityAccessModeSwitchInterface
IsService true
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.SHORT-NAME)}
ModeGroup securityAccess DcmSecurityAccess

c()

8.8.7.8 Dcm_AuthenticationStateModeSwitchInterface

[SWS_Dcm_91074] d
Name Dcm_AuthenticationStateModeSwitchInterface_{Connection}
Comment –
IsService true
Variation Connection = Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDsl
Connection/DcmDslMainConnection.Short-Name
ModeGroup authenticationState DcmAuthenticationState

c()

8.9 External diagnostic service processing

The following chapter applies only to external processed diagnostic services.

8.9.1 <Module>_<DiagnosticService>

[SWS_Dcm_00763] d
Service Name <Module>_<DiagnosticService>
Syntax Std_ReturnType <Module>_<DiagnosticService> (
Dcm_ExtendedOpStatusType OpStatus,
Dcm_MsgContextType* pMsgContext,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x32

Sync/Async Asynchronous
Reentrancy Reentrant
5

415 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_FORCE_
RCRRP_OK DCM_POS_RESPONSE_SENT DCM_POS_
RESPONSE_FAILED DCM_NEG_RESPONSE_SENT DCM_
NEG_RESPONSE_FAILED
Parameters (inout) pMsgContext Message-related information for one diagnostic protocol identifier.
The pointers in pMsgContext shall point behind the SID.
Parameters (out) ErrorCode If the operation <Module>_<DiagnosticService> returns value E_
NOT_OK, the Dcm module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application requests the transmission
of a response Response Pending (NRC 0x78)
Description Callout function. The Dcm shall call this callout function as soon as valid message is received
on relevant DcmDslProtocolRxPduId on SID level. The usecase of multiple diagnostic protocols
will be possible by using different arguments and the function shall be programmed in a way
that it is reentrant. Caller is responsible for the lifetime of the argument pMsgContext. The
name of the callout is defined within parameter DcmDsdSidTabFnc
Available via Dcm_Externals.h

c()

8.9.2 <Module>_<DiagnosticService>_<SubService>

[SWS_Dcm_00764] d
Service Name <Module>_<DiagnosticService>_<SubService>
Syntax Std_ReturnType <Module>_<DiagnosticService>_<SubService> (
Dcm_ExtendedOpStatusType OpStatus,
Dcm_MsgContextType* pMsgContext,
Dcm_NegativeResponseCodeType* ErrorCode
)

Service ID [hex] 0x33

Sync/Async Asynchronous
Reentrancy Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_FORCE_
RCRRP_OK DCM_POS_RESPONSE_SENT DCM_POS_
RESPONSE_FAILED DCM_NEG_RESPONSE_SENT DCM_
NEG_RESPONSE_FAILED
Parameters (inout) pMsgContext Message-related information for one diagnostic protocol identifier.
The pointers in pMsgContext shall point behind the SID.
Parameters (out) ErrorCode If the operation <Module>_<DiagnosticService>_<SubService>
returns value E_NOT_OK, the Dcm module shall send a negative
response with NRC code equal to the parameter ErrorCode
parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application requests the transmission
of a response Response Pending (NRC 0x78)
5

416 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4
Description Callout function. If a DcmDsdSubServiceFnc is configured for the received subservice, the Dcm
shall call this callout function as soon as this subservice is requested. The usecase of multiple
diagnostic protocols will be possible by using different arguments and the function shall be
programmed in a way that it is reentrant. Caller is responsible for the lifetime of the argument p
MsgContext. The name of the callout is defined within parameter DcmDsdSubServiceFnc.
Available via Dcm_Externals.h

c()

8.10 Internal interfaces (not normative)

The following interfaces are used in the Dcm SWS in order to improve the understand-
ing of the Dcm module behavior. An implementation is not required to use these inter-
faces.

8.10.1 DslInternal_SetSecurityLevel

1 void
2 DslInternal_SetSecurityLevel(Dcm_SecLevelType SecurityLevel)

This function sets a new security level value in the Dcm module. NOTE: for the definition
of the parameter, refer to Dcm_GetSecurityLevel.
8.10.2 DslInternal_SetSesCtrlType

1 void
2 DslInternal_SetSesCtrlType(Dcm_SesCtrlType SesCtrlType)

This function sets a new session control type value in the Dcm module. NOTE: for the
definition of the parameter, refer to the Dcm_GetSesCtrlType.
8.10.3 DspInternal_DcmConfirmation

1 void
2 DspInternal_DcmConfirmation(Dcm_IdContextType idContext,
3 uint16 ConnectionId
4 Dcm_ConfirmationStatusType status)

This function confirms the successful transmission or a transmission error of a diag-

nostic service. This is the right time to perform any application state transitions.
This API is also called if the response to a diagnostic service is suppressed.
8.10.4 DslInternal_ResponseOnOneEvent

1 Dcm_StatusType
2 DslInternal_ResponseOnOneEvent(const Dcm_MsgType MsgPtr,
3 Dcm_MsgLenType MsgLen,

417 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

4 uint16 ConnectionId)

This API executes the processing of one event, requested internally in the DCM.
8.10.5 DslInternal_ResponseOnOneDataByPeriodicId

1 Dcm_StatusType
2 DslInternal_ResponseOnOneDataByPeriodicId(uint8 PeriodicId)

This API provides the processing of one periodic ID event, requested internally in the
DCM. The frequency of calling this function depends on the rate given in the original
ReadDataByPeriodicID request (parameter transmissionMode).
8.10.6 DsdInternal_StartPagedProcessing

1 void
2 DsdInternal_StartPagedProcessing(const Dcm_MsgContextType* pMsgContext)

With this API, the DSP submodule gives the complete response length to the Dcm mod-
ule and starts paged-buffer handling. This API starts no transmission!
8.10.7 DspInternal_CancelPagedBufferProcessing

1 void
2 DspInternal_CancelPagedBufferProcessing()

Dcm informs DSP, that processing of paged-buffer was cancelled due to errors. Upon
this call, DSP is not allowed to process further on paged-buffer handling.
8.10.8 DsdInternal_ProcessPage

1 void
2 DsdInternal_ProcessPage(Dcm_MsgLenType FilledPageLen)

DSP requests transmission of filled page.

9 Sequence diagrams

9.1 Overview
For clarification, the following sequence diagrams don’t represent the full communica-
tion mechanism between the Dcm module and the PduR module. This is to keep the
sequence diagrams simple. Before the Dcm_TpRxIndication call, the PduR mod-
ule will ask the Dcm module for a buffer by calling Dcm_StartOfReception and
Dcm_CopyRxData. This exchange is not shown on the next sequence diagrams. Af-
ter a PduR_DcmTransmit() request from the Dcm module to the PduR module, data
exchanges with Dcm_CopyTxData service, are not shown in the sequence diagrams.
The function Xxx_StartProtocol() shall be called with the very first diagnostic request.

418 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

9.2 DSL (Diagnostic Session Layer)

9.2.1 Start Protocol

«module» «module» «module» Dcm User External Module

PduR Dsl Dsd

Dcm_TpRxIndication(PduIdType, Std_ReturnType)

Xxx_StartProtocol(Std_ReturnType, Dcm_ProtocolType,
uint16, uint16)
Dcm_StartProtocol()

alt protocol allowed?

[E_OK] Data_Indication_functionality()
<Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

Data_Indication_functionality()

[E_PROTOCOL_NOT_ALLOWED]

Dcm_TpRxIndication()

Figure 9.1

419 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

9.2.2 Process Busy behavior

«module» «module» «module» External Module «module»

PduR Dsl Dsd Dsp


Dcm_TpRxIndication(PduIdType,
Std_ReturnType)

<Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Data_Indication_functionality() Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

Data_Indication_functionality()

Dcm_TpRxIndication()

alt response?

[negative response: RC=0x78]
 

PduR_DcmTransmit(Std_ReturnType, PduIdType,
const PduInfoType*): Std_ReturnType

PduR_DcmTransmit()

 

PduR_DcmTransmit(Std_ReturnType, PduIdType,
const PduInfoType*): Std_ReturnType

PduR_DcmTransmit()

[positive response]
Dcm_TpTxConfirmation(PduIdType,
NotifResultType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

Figure 9.2

Internally, the DSL submodule calculates the time to response the tester. In the
case that the external module processing the request doesn’t close the request
by returning E_OK or E_NOT_OK to <Module>_<DiagnosticService>() or <Mod-
ule>_<DiagnosticService>_<SubService>() APIs call (in case of normal response han-
dling) or DsdInternal_ProcessPage() (in case of paged-buffer handling) during the
P2ServerMax and/or P2*ServerMax, the DSL submodule sends a negative response
(requestCorectlyReceived-ResponsePending) independently.

420 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

9.2.3 Update Diagnostic Session Control when timeout occurs

«module» «module» «module» External Module «module»

PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,
   
  
Std_ReturnType)
 

Data_Indication_functionality()
<Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

Data_Indication_functionality()

Dcm_TpRxIndication()

Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()


Data_Confimation_functionality()

Dcm_TpTxConfirmation()

Figure 9.3

The DSL submodule resets session control value to default, if in a non-default ses-
sion S3server timeout occurs. S3server timeout timer will be started with every data
confirmation from the PduR module.

421 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

9.2.4 Process single response of ReadDataByPeriodicIdentifier

«module» «module» «module» «module» Dcm User

PduR Dsl Dsd Dsp

ref

  Receive a request message ... - synchronous
  
     
       

ref
Receive a request message ... - asynchronous


                !  "
#!    #      !  $ %

&   DslInternal_ResponseOnOneDataByPeriodicId(uint8)

 
Data_Indication_functionality()

ReadDataByIdentifier service interpreter()

ReadData(Did specific type):

Std_ReturnType

DspInternal_DcmReadDataByIdentifier()



Data_Indication_functionality()

DslInternal_ResponseOnOneDataByPeriodicId()

Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

Figure 9.4

The DSP submodule requests sampling and transmission of Periodic Identifier data,
when an event to Periodic Identifier occurs (i. e. a given time period is over). The DSP
submodule initiates the sending of one periodic identifier calling the function Respon-
seOnOneDataByPeriodicId() provided by the DSL submodule.
Within this function the DSL submodule simulates a "ReadDataByIdentifier" request
for the given PeriodicId. The High byte of the DataIdentifier shall be set to 0xF2 as
specified in [18]) and the low byte is set to value of the PeriodicId.
The ReadData interfaces of the corresponding Datas of the DID are called to get the
DID value. The Dcm module is not able to receive for the same periodic identifier
another event request from the DSP submodule, unless the confirmation of the current
transmission is received.

422 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

9.2.5 Process single event-triggered response of ResponseOnEvent

«module» «module» «module» «module» Dcm User

PduR Dsl Dsd Dsp

ref
Receive a request message ... - synchronous


  
      
        
 ref
Receive a request message ... - asynchronous

                !      

    "  #    #      
     !   

  DslInternal_ResponseOnOneEvent(const Dcm_MsgType, Dcm_MsgLenType, uint16)


Data_Indication_functionality()

ReadDataByIdentifier service interpreter()

ReadData(Did specific type):

Std_ReturnType

  DspInternal_DcmReadDataByIdentifier()

Data_Indication_functionality()

DslInternal_ResponseOnOneEvent()

Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)

Data_Confirmation_functionality()
DspInternal_DcmConfirmation(Dcm_IdContextType, PduIdType,
Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

Figure 9.5

This sequence diagram shows an example for ResponseOnEvent. ResponseOnEvent

is setup and started for onDTCStatusChange. Event changes are reported to the Dcm
which will trigger a serviceToRespondTo.

423 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

9.2.6 Process concurrent requests

«module» «module» «module» External Module «module» Dcm User

PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,

 Std_ReturnType)

Data_Indication_functionality()
<Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)



 Dcm_TpRxIndication(PduIdType,
Std_ReturnType)
Data_Indication_functionality()

Stop_Protocol_functionality()

Xxx_StopProtocol
(Std_ReturnType,
Dcm_ProtocolType, uint16,
uint16) Dcm_StopProtocol()
Stop_Protocol_functionality()
Data_Indication_functionality()

PduR_DcmCancelTransmitRequest()

 PduR_DcmTransmit(Std_ReturnType,

  PduIdType, const PduInfoType*):
Std_ReturnType

PduR_DcmTransmit()

Dcm_TpRxIndication()

<Module>_<DiagnosticService>()

Data_Indication_functionality()

Dcm_TpRxIndication()

  Dcm_TpRxIndication(PduIdType,
Std_ReturnType)

 
 Data_Indication_functionality()
 !

Figure 9.6

On reception of OBD request in parallel to processing of a normal diagnostic request

(e.g enhanced diagnostic protocol, customer diagnostic protocol), running diagnostic
request will be preempted. This is due to the configured higher priority of OBD protocol
(see configuration parameter DcmDslProtocolPriority).
The following is processed on reception of 1st OBD request:
• The Application is informed of the protocol stop (done with Xxx_StopProtocol())
and resets to a stable state (e.g. switch of digital Ios,..).
• Lower Layer is requested to cancel ongoing transmission on the same N-PDU
(done with PduR_DcmCancelTransmitRequest()).

424 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

• If the Dcm is not able to switch fast enough from non OBD to OBD protocol, the DSL
submodule responses with a negative response "BusyRepeatRequest" (NRC
0x21) to OBD tester. It is in the responsibility of the system designer to ensure
that the legislative timings are satisfied.
As long as the external module processing the request is not fin-
ished (finish is indicated by returning E_OK or E_NOT_OK to <Mod-
ule>_<DiagnosticService>()/<Module>_<DiagnosticService>_<SubService>() API
call) or no timeout occurs, the DSL submodule responses with negative response
"BusyRepeatRequest".
With receiving E_OK or E_NOT_OK from the external module to <Mod-
ule>_<DiagnosticService>()/<Module>_<DiagnosticService>_<SubService>() API
call, the DSL submodule will not transmit a response to old request. There will also
not given any negative response to inform first tester about preemption of diagnostic
request.
If the external module processing the request never returns E_OK or E_NOT_OK
to <Module>_<DiagnosticService>()/<Module>_<DiagnosticService>_<SubService>()
API call, the DSL submodule runs into timeout and switches directly to further process-
ing of preempting protocol.

9.2.7 Interface to ComManager

9.2.7.1 Handling in Default Session

«module» «module» «module» External Module «module»

PduR Dcm ComM Dsp

Dcm_TpRxIndication(PduIdType,

 Std_ReturnType)

ComM_DCM_ActiveDiagnostic(NetworkHandleType)

ComM_DCM_ActiveDiagnostic()

<Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

Dcm_TpRxIndication()

  Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)

DspInternal_DcmConfirmation(Dcm_IdContextType, PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

ComM_DCM_InactiveDiagnostic(NetworkHandleType)

ComM_DCM_InactiveDiagnostic()

Dcm_TpTxConfirmation()

Figure 9.7

425 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

9.2.7.2 Handling in Non-Default Session

«module» «module» «module» External Module «module»

PduR Dcm ComM Dsp

Dcm_TpRxIndication(PduIdType,

 Std_ReturnType)

<Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

Dcm_TpRxIndication()

 
Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)

DspInternal_DcmConfirmation(Dcm_IdContextType, PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Dcm_TpTxConfirmation()

Figure 9.8

9.2.7.3 Session transitions

«module» «module»
Dsl ComM

  Session transition: Default to

 Non-Default()

ComM_DCM_ActiveDiagnostic(NetworkHandleType)

ComM_DCM_ActiveDiagnostic()

Session transition: Non-

default to Default()

  ComM_DCM_InactiveDiagnostic(NetworkHandleType)


ComM_DCM_InactiveDiagnostic()

Figure 9.9

426 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

9.2.7.4 Communication States

«module» «module»
ComM Dcm

   Dcm_ComM_NoComModeEntered

(uint8)

Disable Transmission of ROE

and PeriodicID()

Disable normal Transmission

(receive and transmit)
Dcm_ComMNoComModeEntered (PduR_DcmTransmit)
()

 
  Dcm_ComM_SilentComModeEntered
(uint8)

Disable Transmission of ROE

and PeriodicID()

Disable normal transmission

(transmit) (PduR_DcmTransmit)
Dcm_ComMSilentComModeEntered
()

   Dcm_ComM_FullComModeEntered

(uint8)

Enable Transmission of ROE

and PeriodicID()

Enable normal Transmission

(PduR_DcmTransmit)
Dcm_ComMFullComModeEntered
()

Figure 9.10

DSD (Diagnostic Service Dispatcher) Receive a request message and transmit a posi-
tive response message - synchronous transmission

427 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

«module» «module» «module» External Module «module»

PduR Dsl Dsd Dsp

 Dcm_TpRxIndication(PduIdType,
Std_ReturnType)

Data_Indication_functionality()
<Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

 

Data_Indication_functionality()

Dcm_TpRxIndication()

Dcm_TpTxConfirmation(PduIdType,
NotifResultType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

Figure 9.11

Receive a request message and transmit a positive response message - asynchronous

transmission
«module» «module» «module» External Module «module»
PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,

 Std_ReturnType)

Data_Indication_functionality()
<Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

Data_Indication_functionality()

Dcm_TpRxIndication()

Dcm_TpTxConfirmation(PduIdType,

 
NotifResultType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

Figure 9.12

428 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Receive a request message and suppress a positive response

«module» «module» «module» External Module «module»
PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,

 Std_ReturnType)

Data_Indication_functionality() <Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

 
Data_Indication_functionality()

Dcm_TpRxIndication()

Figure 9.13

9.2.8 Receive request message and transmit negative response message

«module» «module» «module» External Module «module»

PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,

 Std_ReturnType)

Data_Indication_functionality()
<Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

 
<Module>_<DiagnosticService>()

Data_Indication_functionality()

Dcm_RxIndication()

Dcm_TpTxConfirmation(PduIdType,
NotifResultType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

Figure 9.14

429 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

9.2.9 Process Service Request with paged-buffer

«module» «module» «module» «module»

PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,


Std_ReturnType)
Data_Indication_functionality()
service interpreter call()

  DsdInternal_StartPagedProcessing(const
Dcm_MsgContextType*)

DspInternal_DcmUpdatePage(Dcm_MsgType, Dcm_MsgLenType)

DspInternal_DcmUpdatePage()

DspInternal_StartPagedProcessing()

service interpreter call()

DsdInternal_ProcessPage(Dcm_MsgLenType)
   PduR_DcmTransmit(Std_ReturnType,
  Transmit_functionality()
PduIdType, const PduInfoType*):
Std_ReturnType

Dcm_CopyTxData(BufReq_ReturnType, PduIdType,
PduInfoType*, RetryInfoType*, PduLengthType*)

Dcm_CopyTxData=BUFREQ_E_BUSY()

loop transmit
Dcm_CopyTxData(BufReq_ReturnType, PduIdType,
PduInfoType*, RetryInfoType*, PduLengthType*)
Data_Confirmation_functionality()
DspInternal_DcmUpdatePage(Dcm_MsgType,
Dcm_MsgLenType)

DsdInternal_ProcessPage(Dcm_MsgLenType)

Transmit_functionality()

Dcm_CopyTxData(BufReq_ReturnType, PduIdType,
PduInfoType*, RetryInfoType*, PduLengthType*)

Dcm_CopyTxData=BUFREQ_OK()

Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)

Data_Confirmation_functionality()
   DspInternal_DcmConfirmation(Dcm_IdContextType,
  PduIdType, Dcm_ConfirmationStatusType)

Figure 9.15

The following flow is processed in case no error occurs on the Application side:

430 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Start of process:
4) DsdInternal_StartPagedProcessing(): With this API, the DSP submodule gives the
complete response length to the Dcm module and starts paged-buffer handling. This
API starts no transmission!
5) UpdatePage(): The Dcm module requests data to be transmitted.
6) DsdInternal_ProcessPage(): With this API, the DSP submodule requests transmis-
sion of the current page.
8) PduR_DcmTransmit(): The Dcm module requests transmission to the lower layers.
9) Dcm_CopyTxData: The buffer is filled and the Dcm module shall return
"BUFREQ_OK"(10).

Start of the loop:

11) Dcm_CopyTxData: The PduR module requests the buffer but the buffer is not
filled by the DSP submodule.
12 + 13) UpdatePage: The Dcm module requests the DSP submodule to fill the next
page.
14) By returning "BUFREQ_E_BUSY", the Dcm module indicates that the buffer has to
be filled by the DSP submodule.
15) DsdInternal_ProcessPage(): With this API, the DSP submodule requests transmis-
sion of the current page.
17) Then, on the next call of Dcm_CopyTxData the buffer is filled and the Dcm module
shall return "BUFREQ_OK" (18).

LOOP: The flow 10 to 18 is repeated as long data can be sent.

End of the loop:
n-2 -> n) Dcm_TpTxConfirmation When all data is send, the PduR module indicates
the sending with a confirmation, which is given to the DSP submodule.
The APIs 4, 5 and 6 are needed only for paged-buffer transmission.
Page buffer timeout handling:

The Dcm module reacts in the following described way, when the DSP submodule starts
paged-buffer handling, but is not able to process further on filling the response data.
E.g. there are problems to access data from an EEPROM device. When providing
the Pagebuffer to the DSP submodule (13: UpdatePage()), and getting a negative Tx
confirmation from underlying Transport Layers, the following error handling is carried
out in the Dcm module:
• The Dcm module stops further processing of paged-buffer (item 15),
• The Dcm module requests the DSP submodule (14: DspInter-
nal_CancelPagedBufferProcessing()) to stop further processing of PagedBuffer.

431 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

«module» «module» «module» «module»

PduR Dsl Dsd Dsp

Dcm_TpRxIndication

 (PduIdType, Std_ReturnType)
Data_Indication_functionality()

DspInternal_Dcm<DiagnosticService>(Dcm_MsgContextType)

  DsdInternal_StartPagedProcessing(const Dcm_MsgContextType*)

DspInternal_DcmUpdatePage(Dcm_MsgType, Dcm_MsgLenType)

DspInternal_DcmUpdatePage()

DsdInternal_StartPagedProcessing()

DspInternal_Dcm<DiagnosticServices>()

DsdInternal_ProcessPage(Dcm_MsgLenType)
PduR_DcmTransmit(Std_ReturnType,
  Transmit_functionality()
 PduIdType, const PduInfoType*):
Std_ReturnType

Dcm_CopyTxData(BufReq_ReturnType, PduIdType,
PduInfoType*, RetryInfoType*, PduLengthType*)

Dcm_CopyTxData=BUFREQ_OK()

loop transmit
Dcm_CopyTxData(BufReq_ReturnType, PduIdType,
PduInfoType*, RetryInfoType*, PduLengthType*)
Data_Confirmation_functionality() DspInternal_DcmUpdatePage(Dcm_MsgType,
Dcm_MsgLenType)

Dcm_CopyTxData=BUFREQ_E_BUSY()

DspInternal_DcmCancelPagedBufferProcessing()

 

 

Data_Failed_Functionality()

Dcm_CopyTxData(BufReq_ReturnType, PduIdType,
PduInfoType*, RetryInfoType*, PduLengthType*)

Dcm_CopyTxData=BUFREQ_E_NOT_OK()

   Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)


Data_Confirmation_functionality() DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

Figure 9.16

9.2.10 Process copy data in reception

Please refer to Figure 9 "CanTp I-PDU reception" in [11, SWS PduR].

432 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

9.2.11 Process copy data in transmission

Please refer to Figure 14 "CanTp I-PDU transmission" in [11, SWS PduR].

9.3 DSP (Diagnostic Service Processing)

9.3.1 Interface DSP - DEM (service 0x19, 0x14, 0x85)

Please refer to Section 9 in [13, SWS Dem].

9.3.2 Interface special services

9.3.2.1 Process Diagnostic Session Control

«module» «module» «module» «module»

PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,
Std_ReturnType)

Data_Indication_functionality()

DiagnosticSessionControl service
interpreter()

Data_Indication_functionality()

Dcm_TpRxIndication()

Dcm_TpTxConfirmation(PduIdType,
Std_ReturnType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

Figure 9.17

Above sequence diagram shows processing of Diagnostic Session Control request

from a tester. Note that the new diagnostic session and timing parameters only apply
after the transmission confirmation of the server positive response

433 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

9.3.2.2 Process Tester Present

«module» «module» «module» «module»

PduR Dsl Dsd Dsp

 Dcm_TpRxIndication(PduIdType,
  Std_ReturnType)
  
  Data_Indication_functionality()
TesterPresent service
interpreter()

TesterPresent service
interpreter()

Data_Indication_functionality()

Dcm_TpRxIndication()

Dcm_TpRxIndication(PduIdType,


  Std_ReturnType)
 
  Data_Indication_functionality()

TesterPresent service
interpreter()

TesterPresent service
interpreter()

Data_Indication_functionality()

Dcm_TpRxIndication()

Figure 9.18

Above sequence diagram shows processing of TesterPresent commands, which are

not of type functional addressed with subfunction 0x80. These TesterPresent com-
mands are interpreted in the DSL submodule (more details can be found in Section
7.4.4.3 Concurrent TesterPresent keep alive logic").
All the other TesterPresent commands are processed in the following way: On a com-
mand TesterPresent the DSD submodule calls the DSP submodule with the function
TesterPresent(). The sequence chart also shows the case when an error occurs and a
negative response is sent.

434 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

9.3.2.3 Process Security Access

«module» «module» «module» «module» Dcm User

PduR Dsl Dsd Dsp

  Dcm_TpRxIndication(PduIdType,

Std_ReturnType)

Data_Indication_functionality()

SecurityAccess service
interpreter()

GetSeed(Std_ReturnType, uint8*, Dcm_OpStatusType, uint8*,

Dcm_NegativeResponseCodeType*)

GetSeed()

  Dcm_TpRxIndication(PduIdType,

Std_ReturnType)

Data_Indication_functionality()
SecurityAccess service
interpreter()

CompareKey(Std_ReturnType,
uint8*, Dcm_OpStatusType)

Dcm_CompareKey()

Dcm_SetSecurityLevel(Dcm_SecLevelType)

Dcm_SetSecurityLevel()

Figure 9.19

To get the security access, the DSD submodule has to call the DSP submodule to get
the seed value from the application. If no error is detected, the seed value is sent in
the positive response.
In a second step, the DSP submodule gets the key calculated by the tester and requests
the application to compare this key with the internal calculated key. If no error occurs,
the new access type is set in the DSL submodule and a positive response is sent.

435 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

9.3.2.4 Process ResponseOnEvent OnDtcChange

«module» «module» «module» «module» Dcm User

PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,
Std_ReturnType)
Data_Indication_functionality()

ResponseOnEvent service
interpreter()

  
ResponseOnEvent service
 
Data_Indication_functionality() interpreter()
Dcm_TpRxIndication()
Configure Event()

    

Dcm_TpRxIndication(PduIdType,    
Std_ReturnType)

Data_Indication_functionality()
ResponseOnEvent service
interpreter()
 
 
 
ResponseOnEvent service
Data_Indication_functionality() interpreter()
Internal activation of DTC
Dcm_TpRxIndication() status supervision()

Dcm_DemTriggerOnDTCStatus()

Check DTC and

Status()

alt If DTC and Status fit to ROE configuration

DslInternal_ResponseOnOneEvent(MsgPtr,MsgLen,DcmRxPduId)
[TRUE]

Data_Indication_functionality()

ReadDTCInformation
service interpreter()

Dcm_DemTriggerOnDTCStatus()

[FALSE]

Dcm_TpRxIndication(PduIdType,
Std_ReturnType)

Data_Indication_functionality() ResponseOnEvent service

interpreter()

 
 

 
Data_Indication_functionality() ResponseOnEvent service
Dcm_TpRxIndication() interpreter()

Internal deactivation of
DTC status supervision()

Figure 9.20

Above sequence diagram shows processing of ResponseOnEvent service for sub-

service OnDtcChange.
After configuration and activation of the event by the service ResponseOnEvent, the
Dcm checks the status of the configured DTC on every call to interface Dcm_DemTrig-
gerOnDTCStatus in order to identify if the event shall be trigger. This interface is
called by DEM for any DTC status change and independing of the activation/unactiva-
tion of ResponseOnEvent.

436 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

9.3.2.5 Process ResponseOnEvent OnChangeOfDataIdentifier

«module» «module» «module» «module» Dcm User

PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,
Std_ReturnType)
Data_Indication_functionality()
ResponseOnEvent service
interpreter()


     
 

ResponseOnEvent service
Data_Indication_functionality() interpreter()
Dcm_TpRxIndication()
Configure Event()

    
  
Dcm_TpRxIndication(PduIdType,
Std_ReturnType)
Data_Indication_functionality()
ResponseOnEvent service   

interpreter()  

ResponseOnEvent service
interpreter()
Data_Indication_functionality()

Dcm_TpRxIndication()

Dcm_TriggerOnEvent(Eventid)

DslInternal_ResponseOnOneEvent(MsgPtr, MsgLen, DcmRxPduId)

Data_Indication_functionality()

DspInternal_DcmReadDataByIdentifier(pMsgContext)

Xxx_ReadData()

Xxx_ReadData()

Dcm_TriggerOnEvent()
Dcm_TpRxIndication(PduIdType,
Std_ReturnType)
Data_Indication_functionality() ResponseOnEvent service
interpreter()
 

 
Data_Indication_functionality() ResponseOnEvent service
Dcm_TpRxIndication() interpreter()

Figure 9.21

Above sequence diagram shows processing of ResponseOnEvent service for sub-

service OnChangeOfDataIdentifier in the case the event is externally managed (The
event can be internally managed, but is not describe in this diagram).
After configuration and etxernal activation of the event by the service ResponseOn-
Event, the Dcm wait to be trigger by the external module managing this DID.

437 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

9.3.2.6 Process Jump to Bootloader

«module» «module» «module» «module» «module»

PduR Dsl Dsd Dsp Dcm_Callouts

Dcm_TpRxIndication(PduIdType,
Std_ReturnType)

Data_Indication_functionality()

DiagnosticSessionControl service
interpreter()

DiagnosticSessionControl service
interpreter()

Data_Indication_functionality()

Dcm_TpRxIndication()

alt if Reset allowed

[TRUE]

Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType, PduIdType,
Dcm_ConfirmationStatusType)

Dcm_SetProgConditions()

Dcm_SetProgConditions()

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

[FALSE]

Figure 9.22

Above sequence diagram shows processing of a jump to bootloader on reception of

DiagnosticSessionControl. On reception of DiagnosticSessionControl, the Dcm checks
if the requested session is configured to trigger a jump to bootloader. In positive case,
the Dcm start the jump to bootloader process:
• Transmission of NRC 0x78 (ResponsePending)
• On confirmation of transmission of NRC 0x78, the Dcm calls the callout DcmSet-
ProgConditions to store all information needed for the bootloader

10 Configuration specification
In general, this chapter defines configuration parameters and their clustering into con-
tainers. In order to support the specification Chapter 10.1 describes fundamentals.

438 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

It also specifies a template (table) you shall use for the parameter specification. We
intend to leave Chapter 10.1 in the specification to guarantee comprehension.
Chapter 10.2 specifies the structure (containers) and the parameters of the module
<MODULE_ABBREVIATION>.
Chapter 10.4 specifies published information of the module <MOD-
ULE_ABBREVIATION>.

10.1 How to read this chapter

For details refer to the chapter 10.1 "Introduction to configuration specification" in
SWS_BSWGeneral [7].

10.2 Containers and configuration parameters

The following chapters summarize all configuration parameters. The detailed meanings
of the parameters describe Chapter 7 and Chapter 8.

439 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

AUTOSARParameterDefinition:
EcucDefinitionCollection

+module

Dcm: EcucModuleDef

upperMultiplicity = 1
lowerMultiplicity = 0

+container +container

DcmConfigSet: EcucParamConfContainerDef DcmGeneral:

EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmDsd:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmDsl:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmPageBufferCfg:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmDsp:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmProcessingConditions:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.1: Configuration overview

10.2.1 Dcm

440 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Module SWS Item ECUC_Dcm_01082

Module Name Dcm
Module Description Configuration of the Dcm (Diagnostic Communications Manager)
module.
Post-Build Variant true
Support
Supported Config VARIANT-LINK-TIME, VARIANT-POST-BUILD, VARIANT-PRE-
Variants COMPILE
Included Containers
Container Name Multiplicity Scope / Dependency
DcmConfigSet 1 This container contains the configuration parameters
and sub containers of the DCM module supporting
multiple configuration sets.
DcmGeneral 1 Contains general configuration parameters valid for
the entire Dcm module.

10.2.2 DcmConfigSet

SWS Item [ECUC_Dcm_00819]

Container Name DcmConfigSet
Parent Container Dcm
Description This container contains the configuration parameters and sub
containers of the DCM module supporting multiple configuration sets.
Configuration Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDsd 1 These parameters configure the Diagnostic Service
Dispatcher submodule.
DcmDsl 1 These parameters configure the Diagnostic Session
Layer submodule.
DcmDsp 0..1 These parameters apply to Diagnostic Service
Processing. There will always be one set of these
parameters per Dcm. Please note: Although the
multiplicity is set to 0..1. It can be expected that this
container exists in any valid DCM configuration.
DcmPageBufferCfg 1 This container contains the configuration (parameters)
for Page Buffer handling
DcmProcessing 0..1 This container contains the configuration for mode
Conditions arbitration functionality of the Dcm

10.2.2.1 DcmPageBufferCfg

SWS Item [ECUC_Dcm_00775]

Container Name DcmPageBufferCfg
Parent Container DcmConfigSet
Description This container contains the configuration (parameters) for Page Buffer
handling
Configuration Parameters

441 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmPagedBufferEnabled [ECUC_Dcm_00776]

Parent Container DcmPageBufferCfg
Description Allow to enable or disable the Paged buffer mechanism. true = Paged
buffer handling enabled false = Paged Buffer handling disabled
Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

No Included Containers
DcmPageBufferCfg: DcmPagedBufferEnabled:
EcucParamConfContainerDef EcucBooleanParamDef
+parameter
lowerMultiplicity = 1 upperMultiplicity = 1
upperMultiplicity = 1 lowerMultiplicity = 1

Figure 10.2: DcmPageBufferCfg configuration overview

10.2.2.2 DcmProcessingConditions

SWS Item [ECUC_Dcm_00932]

Container Name DcmProcessingConditions
Parent Container DcmConfigSet
Description This container contains the configuration for mode arbitration
functionality of the Dcm
Configuration Parameters

442 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmModeCondition 1..* This container contains the configuration of a mode
condition or an environmental conditions which can be
used as argument in DcmModeRules.

One DcmModeCondition shall contain either one

DcmSwcModeRef or one DcmBswModeRef or one
DcmSwcSRDataElementRef.

Please note that the Dcm acts as well as mode

manager. Therefore the references DcmSwcModeRef or
one DcmBswModeRef. might point to provided
ModeDeclarationGroupPrototypes of the Dcm itself as
well as to provided ModeDeclarationGroupPrototypes of
other Bsw Modules or software components.

In case of a configured DcmSwcModeRef or

DcmBswModeRef only the DcmConditionType
DCM_EQUALS or DCM_EQUALS_NOT are applicable.

In case of DcmSwcSRDataElementRef all literals of

DcmConditionType are possible.
DcmModeRule 1..* This container contains the configuration of a mode rule
which represents a logical expression with
DcmModeConditions or other DcmModeRules as
arguments.

All arguments are processed with the operator defined

by DcmLogicalOperator, for instance: Argument_A AND
Argument_B AND Argument_C

443 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmProcessingConditions:
EcucParamConfContainerDef +subContainer DcmLogicalOperator:
DcmModeRule: EcucParamConfContainerDef EcucEnumerationParamDef
lowerMultiplicity = 0 +parameter
lowerMultiplicity = 1 lowerMultiplicity = 0
upperMultiplicity = 1
upperMultiplicity = * upperMultiplicity = 1

+destination +literal

DCM_OR:
EcucEnumerationLiteralDef
+literal

+reference DCM_AND:
+parameter EcucEnumerationLiteralDef

DcmArgumentRef: DcmModeRuleNrcValue:
+subContainer EcucChoiceReferenceDef EcucIntegerParamDef

DcmModeCondition: upperMultiplicity = * lowerMultiplicity = 0

EcucParamConfContainerDef +destination lowerMultiplicity = 1 upperMultiplicity = 1
requiresIndex = true min = 1
lowerMultiplicity = 1 max = 255
upperMultiplicity = *

DCM_EQUALS:
EcucEnumerationLiteralDef
+literal

DCM_GREATER_THAN:
EcucEnumerationLiteralDef
+literal

DCM_EQUALS_NOT:
EcucEnumerationLiteralDef
+literal

DCM_LESS_THAN:
EcucEnumerationLiteralDef
+literal

DCM_LESS_OR_EQUAL:
EcucEnumerationLiteralDef
+literal

DCM_GREATER_OR_EQUAL: +literal
EcucEnumerationLiteralDef DcmConditionType: EcucEnumerationParamDef

lowerMultiplicity = 1
upperMultiplicity = 1

+parameter

DcmModeConditionCertificateCompareElementRef: KeyMCertificateElement:
+reference EcucReferenceDef +destination EcucParamConfContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = 65535
requiresSymbolicNameValue = true
(from KeyM)

Figure 10.3: DcmDspProcessingConditions1 configuration overview

DcmModeCondition: DcmSwcSRDataElementRef:
EcucParamConfContainerDef EcucChoiceReferenceDef DcmDspPidService01ExternalSRDataElementClass:
+destination
+reference EcucChoiceContainerDef
lowerMultiplicity = 1 upperMultiplicity = 1
upperMultiplicity = * lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspPidService01:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+destination

DcmDspExternalSRDataElementClass: DcmDspData:
EcucChoiceContainerDef +subContainer EcucParamConfContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = *

+subContainer
DcmSwcDataElementPrimitive:
DcmSwcDataElementValue: EcucParamConfContainerDef +parameter DcmSwcDataElementPrimitiveValue:
+choice
EcucChoiceContainerDef EcucIntegerParamDef
lowerMultiplicity = 0
upperMultiplicity = 1

DcmSwcDataElementArray:
+choice EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer DcmSwcDataElementArrayElementIndex:
EcucIntegerParamDef
+parameter
DcmSwcDataElementArrayElement:
EcucParamConfContainerDef

lowerMultiplicity = 0 +parameter
upperMultiplicity = * DcmSwcDataElementArrayElementValue:
EcucIntegerParamDef

+reference

DcmBswModeRef: EcucInstanceReferenceDef

lowerMultiplicity = 0
upperMultiplicity = 1
destinationType = MODE-DECLARATION
destinationContext = MODE-DECLARATION-GROUP-PROTOTYPE

+reference

DcmSwcModeRef: EcucInstanceReferenceDef

lowerMultiplicity = 0
upperMultiplicity = 1
destinationType = MODE-DECLARATION
destinationContext = ROOT-SW-COMPOSITION-PROTOTYPE SW-COMPONENT-PROTOTYPE P-PORT-PROTOTYPE MODE-DECLARATION-GROUP-PROTOTYPE

Figure 10.4: DcmDspProcessingConditions2 configuration overview

444 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

10.2.3 DcmDsd

10.2.3.1 DcmDsd

SWS Item [ECUC_Dcm_00688]

Container Name DcmDsd
Parent Container DcmConfigSet
Description These parameters configure the Diagnostic Service Dispatcher
submodule.
Configuration Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDsdServiceRequest 0..* The name of this container is used to define the name of
ManufacturerNotification the R-Port through which the DCM accesses the
interface ServiceRequestNotification. The R-Port is
named
ServiceRequestManufacturerNotification_{Name} where
{Name} is the name of the container
DcmDsdServiceRequestManufacturerNotification.

The lowerMultiplicity is 0: If container

DcmDsdServiceRequestManufacturerNotification does
not exist the Indication API is not available.
DcmDsdServiceRequest 0..* The name of this container is used to define the name of
SupplierNotification the R-Port through which the DCM accesses the
interface ServiceRequestNotification. The R-Port is
named ServiceRequestSupplierNotification_<SWC>
where <SWC> is the name of the container
DcmDsdServiceRequestSupplierNotification.

The lowerMultiplicity is 0: If the container

DcmDsdRequestSupplierNotification does not exist the
Indication API is not available.
DcmDsdServiceTable 1..256 This container contains the configuration (DSD
parameters) for a Service Identifier Table.

Note: It is allowed to add OBD services to a

DcmDsdServiceTable related to a UDS Protocol. But it
is not allowed to add UDS services to a
DcmDsdServiceTable related to an OBD Protocol.

445 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDsd:
EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1

+subContainer
DcmDsdSidTabId:
DcmDsdServiceTable: EcucIntegerParamDef
EcucParamConfContainerDef +parameter
max = 255
upperMultiplicity = 256 min = 0
lowerMultiplicity = 1 upperMultiplicity = 1
lowerMultiplicity = 1

DcmDsdServiceRole: DcmDsdServiceUsed:
EcucIntegerParamDef EcucBooleanParamDef
min = 0 upperMultiplicity = 1
max = 4294967295 lowerMultiplicity = 1
lowerMultiplicity = 0 defaultValue = true
upperMultiplicity = 1
+parameter
+parameter

DcmDsdSidTabServiceId: DcmDsdSidTabSubfuncAvail: DcmDsdSidTabFnc:

EcucIntegerParamDef EcucBooleanParamDef EcucFunctionNameDef

max = 255 upperMultiplicity = 1 lowerMultiplicity = 0

min = 0 lowerMultiplicity = 1 upperMultiplicity = 1
upperMultiplicity = 1
lowerMultiplicity = 1 +parameter +parameter

+parameter

+subContainer

DcmDsdService: EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 1

+reference +reference +reference

DcmDsdSidTabSessionLevelRef: DcmDsdSidTabSecurityLevelRef: DcmDsdSidTabModeRuleRef:

EcucReferenceDef EcucReferenceDef EcucReferenceDef

lowerMultiplicity = 0 lowerMultiplicity = 0 lowerMultiplicity = 0

upperMultiplicity = * upperMultiplicity = * upperMultiplicity = 1

+destination +destination +destination

DcmDspSessionRow: DcmDspSecurityRow: DcmModeRule:

EcucParamConfContainerDef EcucParamConfContainerDef EcucParamConfContainerDef
upperMultiplicity = 31 upperMultiplicity = 31 lowerMultiplicity = 1
lowerMultiplicity = 0 lowerMultiplicity = 0 upperMultiplicity = *

+parameter +parameter

DcmDspSessionLevel: DcmDspSecurityLevel:
EcucIntegerParamDef EcucIntegerParamDef

max = 126 max = 63

min = 1 min = 1
lowerMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = 1
symbolicNameValue = true symbolicNameValue = true

Figure 10.5: DcmDsd configuration overview

446 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Dcm: EcucModuleDef DcmDsd: DcmDsdServiceRequestManufacturerNotification:

EcucParamConfContainerDef +subContainer EcucParamConfContainerDef
upperMultiplicity = 1
lowerMultiplicity = 0 lowerMultiplicity = 1 requiresIndex = true
upperMultiplicity = 1 upperMultiplicity = *
lowerMultiplicity = 0

+container DcmDsdServiceRequestSupplierNotification:
+subContainer EcucParamConfContainerDef
DcmConfigSet: EcucParamConfContainerDef +subContainer
requiresIndex = true
upperMultiplicity = *
lowerMultiplicity = 0

Figure 10.6: DcmDsdIndication configuration overview

10.2.3.2 DcmDsdService

SWS Item [ECUC_Dcm_00689]

Container Name DcmDsdService
Parent Container DcmDsdServiceTable
Description This container contains the configuration (DSD parameters) for a
Service.
Configuration Parameters

Name DcmDsdServiceRole [ECUC_Dcm_01139]

Parent Container DcmDsdService
Description Bitfield were each bit represents one dedicated role. A diagnostic
service is granted access if the bit value is 1. If a bit value is 0, the
service is not allowed to be executed for that role.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 4294967295
Default Value
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

447 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDsdServiceUsed [ECUC_Dcm_01044]

Parent Container DcmDsdService
Description Allows to activate or deactivate the usage of a Service. This parameter
can be used for multi-purpose ECUs.

true - service is available

false - service is not available

Multiplicity 1
Type EcucBooleanParamDef
Default Value true
Post-Build Variant true
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name DcmDsdSidTabFnc [ECUC_Dcm_00777]

Parent Container DcmDsdService
Description Callback function of the ECU Supplier specific component for the
particular service. The function’s prototype is as described for
<Module>_<DiagnosticService>. If this parameter is not configured,
the service is handled Dcm-internally.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

448 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDsdSidTabServiceId [ECUC_Dcm_00735]

Parent Container DcmDsdService
Description Identifier of the service.

The possible service identifiers are defined in ISO 14229-1 and ISO
15031-5.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDsdSidTabSubfuncAvail [ECUC_Dcm_00737]

Parent Container DcmDsdService
Description Information about whether the service has subfunctions or not. This
parameter is used for the handling of the
"suppressPosRspMsgIndicationBit" as defined in ISO 14229-1, which
can be used as a reference for the configuration.

true - service has subfunctions, suppressPosRspMsgIndicationBit is

available

false - service has no subfunctions, suppressPosRspMsgIndicationBit

is not available
Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDsdSidTabModeRuleRef [ECUC_Dcm_00918]

Parent Container DcmDsdService
Description Reference to a DcmDspModeRule which controls the execution of the
service. If there is no reference configured, no mode rule check shall
be performed.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity

449 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Post-Build Variant false

Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDsdSidTabSecurityLevelRef [ECUC_Dcm_00733]

Parent Container DcmDsdService
Description Reference to a Security Level in which the service is allowed to be
executed. Multiple references are allowed for a service.

Please refer to ISO 14229-1, ISO 15031-5 and chapter "Verification of

the Service Security Access levels."

If there is no reference configured, no service security verification shall

be performed.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

450 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDsdSidTabSessionLevelRef [ECUC_Dcm_00734]

Parent Container DcmDsdService
Description Reference to a Session Level in which the service is allowed to be
executed. Multiple references are allowed for a service.

Please refer to ISO 14229-1, ISO 15031-5 and chapter "Verification of

the Diagnostic Session".

If there is no reference configured, no diagnostic session verification

shall be performed.
Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDsdSubService 0..* This container contains the configuration (DSD
parameters) for a subservice of a service. Only those
services may have subservices, which have the
DcmDsdSidTabSubfuncAvail configured as TRUE.

10.2.3.3 DcmDsdServiceRequestManufacturerNotification

SWS Item [ECUC_Dcm_00681]

Container Name DcmDsdServiceRequestManufacturerNotification
Parent Container DcmDsd
Description The name of this container is used to define the name of the R-Port
through which the DCM accesses the interface
ServiceRequestNotification. The R-Port is named
ServiceRequestManufacturerNotification_{Name} where {Name} is the
name of the container
DcmDsdServiceRequestManufacturerNotification.

The lowerMultiplicity is 0: If container

DcmDsdServiceRequestManufacturerNotification does not exist the
Indication API is not available.

Attributes:
requiresIndex=true
Configuration Parameters

451 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

No Included Containers

10.2.3.4 DcmDsdServiceRequestSupplierNotification

SWS Item [ECUC_Dcm_00816]

Container Name DcmDsdServiceRequestSupplierNotification
Parent Container DcmDsd
Description The name of this container is used to define the name of the R-Port
through which the DCM accesses the interface
ServiceRequestNotification. The R-Port is named
ServiceRequestSupplierNotification_<SWC> where <SWC> is the
name of the container DcmDsdServiceRequestSupplierNotification.

The lowerMultiplicity is 0: If the container

DcmDsdRequestSupplierNotification does not exist the Indication API
is not available.

Attributes:
requiresIndex=true
Configuration Parameters

No Included Containers

10.2.3.5 DcmDsdServiceTable

SWS Item [ECUC_Dcm_00732]

Container Name DcmDsdServiceTable
Parent Container DcmDsd
Description This container contains the configuration (DSD parameters) for a
Service Identifier Table.

Note: It is allowed to add OBD services to a DcmDsdServiceTable

related to a UDS Protocol. But it is not allowed to add UDS services to
a DcmDsdServiceTable related to an OBD Protocol.
Configuration Parameters

Name DcmDsdSidTabId [ECUC_Dcm_00736]

Parent Container DcmDsdServiceTable
Description Due to using possibly more service tables, the unique
DcmDsdSidTabId can be used to identify them.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value

452 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDsdService 1..* This container contains the configuration (DSD
parameters) for a Service.

Note : The Dcm internal interaction with the DSP is implementation specific and there-
fore not explicitly configured.

10.2.3.6 DcmDsdSubService

SWS Item [ECUC_Dcm_00802]

Container Name DcmDsdSubService
Parent Container DcmDsdService
Description This container contains the configuration (DSD parameters) for a
subservice of a service. Only those services may have subservices,
which have the DcmDsdSidTabSubfuncAvail configured as TRUE.
Configuration Parameters

Name DcmDsdSubServiceFnc [ECUC_Dcm_00942]

Parent Container DcmDsdSubService
Description Callback function of the ECU Supplier specific component for the
particular service. The function’s prototype is as described for
<Module>_<DiagnosticService>_<SubService>.

If this parameter is not configured, the subservice is handled

Dcm-internally.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –

453 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDsdSubServiceId [ECUC_Dcm_00803]

Parent Container DcmDsdSubService
Description Identifier of the subservice.

The possible subservice identifiers are defined in ISO 14229-1 and ISO
15031-5.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 127
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDsdSubServiceRole [ECUC_Dcm_01140]

Parent Container DcmDsdSubService
Description Bitfield were each bit represents one dedicated role. A sub-function of
a diagnostic service is granted access if the bit value is 1. If a bit value
is 0, the service is not allowed to be executed for that role.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 4294967295
Default Value
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

454 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDsdSubServiceUsed [ECUC_Dcm_01047]

Parent Container DcmDsdSubService
Description Allows to activate or deactivate the usage of a Subservice. This
parameter can be used for multi-purpose ECUs.

true - subservice is available false - subservice is not available.

Multiplicity 1
Type EcucBooleanParamDef
Default Value true
Post-Build Variant true
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name DcmDsdSubServiceModeRuleRef [ECUC_Dcm_00924]

Parent Container DcmDsdSubService
Description Reference to a DcmDspModeRule which controls the execution of the
subservice.

If there is no reference configured, no mode rule check shall be

performed.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

455 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDsdSubServiceSecurityLevelRef [ECUC_Dcm_00812]

Parent Container DcmDsdSubService
Description Reference to a Security Level in which the subservice is allowed to be
executed. Multiple references are allowed for a subservice.

Please refer to ISO 14229-1, ISO 15031-5 and chapter "Verification of

the Service Security Access levels."

If there is no reference configured, no subservice security verification

shall be performed.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDsdSubServiceSessionLevelRef [ECUC_Dcm_00804]

Parent Container DcmDsdSubService
Description Reference to a Session Level in which the subservice is allowed to be
executed. Multiple references are allowed for a subservice.

Please refer to ISO 14229-1, ISO 15031-5 and chapter "Verification of

the Diagnostic Session".

If there is no reference configured, no diagnostic session verification

shall be performed.
Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

456 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

No Included Containers
DcmDsdServiceTable:
EcucParamConfContainerDef

upperMultiplicity = 256
lowerMultiplicity = 1

DcmDsdSubServiceRole:
+subContainer EcucIntegerParamDef

min = 0
DcmDsdService: max = 4294967295
EcucParamConfContainerDef lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = 1
lowerMultiplicity = 1
+parameter

DcmDsdSubServiceId: DcmDsdSubServiceFnc: DcmDsdSubServiceUsed:

EcucIntegerParamDef EcucFunctionNameDef EcucBooleanParamDef

min = 0 lowerMultiplicity = 0 upperMultiplicity = 1

max = 127 upperMultiplicity = 1 lowerMultiplicity = 1
lowerMultiplicity = 1 defaultValue = true
upperMultiplicity = 1

+parameter +parameter +parameter

+subContainer

DcmDsdSubService: EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

+reference +reference +reference

DcmDsdSubServiceSessionLevelRef: DcmDsdSubServiceSecurityLevelRef: DcmDsdSubServiceModeRuleRef:

EcucReferenceDef EcucReferenceDef EcucReferenceDef

lowerMultiplicity = 0 lowerMultiplicity = 0 lowerMultiplicity = 0

upperMultiplicity = * upperMultiplicity = * upperMultiplicity = 1

+destination +destination +destination

DcmDspSessionRow: DcmDspSecurityRow: DcmModeRule:

EcucParamConfContainerDef EcucParamConfContainerDef EcucParamConfContainerDef

upperMultiplicity = 31 upperMultiplicity = 31 lowerMultiplicity = 1

lowerMultiplicity = 0 lowerMultiplicity = 0 upperMultiplicity = *

+parameter +parameter

DcmDspSessionLevel: DcmDspSecurityLevel:
EcucIntegerParamDef EcucIntegerParamDef

max = 126 max = 63

min = 1 min = 1
lowerMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = 1
symbolicNameValue = true symbolicNameValue = true

Figure 10.7: DcmDsdSubService configuration overview

10.2.4 DcmDsl

10.2.4.1 DcmDsl

SWS Item [ECUC_Dcm_00690]

Container Name DcmDsl
Parent Container DcmConfigSet
Description These parameters configure the Diagnostic Session Layer submodule.
Configuration Parameters

457 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDslBuffer 1..256 This container contains the configuration of a diagnostic
buffer.
DcmDslCallbackDCM 0..* Each DcmDslCallbackDCMRequestService container
RequestService defines an R-Port with the
CallbackDCMRequestServices interface which the Dcm
uses to ask permission for protocol changes from the
application software. The R-Port has the name
CallbackDCMRequestServices_<SWC> where <SWC>
is the name of this container.
DcmDslDiagResp 1 This container contains the configuration of the
automatic requestCorrectlyReceivedResponsePending
response management in the Dcm.
DcmDslProtocol 1 This container contains the configurations of the
diagnostic protocols used in Dcm.

Dcm: EcucModuleDef DcmDsl:

upperMultiplicity = 1 EcucParamConfContainerDef
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1

DcmDslProtocol: DcmDslBuffer:
EcucParamConfContainerDef EcucParamConfContainerDef
+subContainer +subContainer
upperMultiplicity = 1 upperMultiplicity = 256
lowerMultiplicity = 1 lowerMultiplicity = 1

DcmDslDiagResp:
EcucParamConfContainerDef
+subContainer
upperMultiplicity = 1
lowerMultiplicity = 1

DcmDslCallbackDCMRequestService:
EcucParamConfContainerDef
+subContainer
lowerMultiplicity = 0
upperMultiplicity = *

Figure 10.8: DcmDsl configuration overview

10.2.4.2 DcmDslBuffer

SWS Item [ECUC_Dcm_00739]

Container Name DcmDslBuffer
Parent Container DcmDsl
Description This container contains the configuration of a diagnostic buffer.
Configuration Parameters

458 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDslBufferSize [ECUC_Dcm_00738]

Parent Container DcmDslBuffer
Description Size of the diagnostic buffer in bytes.

For a linear buffer the size shall be as large as the longest diagnostic
message (request or response).

For a paged buffer the size has impacts on the application

performance.
Multiplicity 1
Type EcucIntegerParamDef
Range 8 .. 4294967294
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

No Included Containers
Dcm: EcucModuleDef

upperMultiplicity = 1
lowerMultiplicity = 0

DcmDsl: DcmDslBuffer: DcmDslBufferSize:

EcucParamConfContainerDef EcucParamConfContainerDef EcucIntegerParamDef
+subContainer +parameter
lowerMultiplicity = 1 upperMultiplicity = 256 max = 4294967294
upperMultiplicity = 1 lowerMultiplicity = 1 min = 8
lowerMultiplicity = 1
upperMultiplicity = 1

Figure 10.9: DcmDslBuffer configuration overview

10.2.4.3 DcmDslCallbackDCMRequestService

SWS Item [ECUC_Dcm_00679]

Container Name DcmDslCallbackDCMRequestService
Parent Container DcmDsl
Description Each DcmDslCallbackDCMRequestService container defines an
R-Port with the CallbackDCMRequestServices interface which the
Dcm uses to ask permission for protocol changes from the application
software. The R-Port has the name
CallbackDCMRequestServices_<SWC> where <SWC> is the name of
this container.
Configuration Parameters

No Included Containers

459 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

10.2.4.4 DcmDslDiagResp

SWS Item [ECUC_Dcm_00691]

Container Name DcmDslDiagResp
Parent Container DcmDsl
Description This container contains the configuration of the automatic
requestCorrectlyReceivedResponsePending response management in
the Dcm.
Configuration Parameters

Name DcmDslDiagRespMaxNumRespPend [ECUC_Dcm_00693]

Parent Container DcmDslDiagResp
Description Maximum number of negative responses with response code 0x78
(requestCorrectlyReceivedResponsePending) allowed for a request. If
Dcm reaches this limit, an automatic 0x10 (generalReject) final
response will be trasmitted and the service processing will be
cancelled. Value 0x00 means that no NRC 0x78 response will be
transmitted.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDslDiagRespOnSecondDeclinedRequest [ECUC_Dcm_00914]

Parent Container DcmDslDiagResp
Description Defines the reaction upon a second request (ClientB) that can not be
processed (e.g. due to priority assessment).

TRUE: when the second request (Client B) can not be processed, it

shall be answered with NRC21 BusyRepeatRequest.

FALSE: when the second request (Client B) can not be processed, it

shall not be responded.
Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

460 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

No Included Containers

10.2.4.5 DcmDslProtocol

SWS Item [ECUC_Dcm_00694]

Container Name DcmDslProtocol
Parent Container DcmDsl
Description This container contains the configurations of the diagnostic protocols
used in Dcm.
Configuration Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDslProtocolRow 1..* This container contains the configuration of one
particular diagnostic protocol used in Dcm.

461 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Dcm: EcucModuleDef DcmDslProtocol:

EcucParamConfContainerDef
upperMultiplicity = 1
DcmDsl:
lowerMultiplicity = 0 +subContainer upperMultiplicity = 1
EcucParamConfContainerDef
lowerMultiplicity = 1
lowerMultiplicity = 1
upperMultiplicity = 1 DcmDslConnection:
+container
+subContainer EcucChoiceContainerDef
DcmConfigSet: lowerMultiplicity = 1
EcucParamConfContainerDef upperMultiplicity = *

+subContainer
DcmTimStrP2StarServerAdjust: DcmDspProtocolEcuAddr: DcmDslProtocolMaximumResponseSize:
EcucFloatParamDef EcucIntegerParamDef EcucIntegerParamDef

min = 0 min = 0 max = 65535

lowerMultiplicity = 1 max = 65535 min = 1
upperMultiplicity = 1 lowerMultiplicity = 0 lowerMultiplicity = 0
max = 5 upperMultiplicity = 1 upperMultiplicity = 1
defaultValue = 4095 DcmDslProtocolPriority:
+parameter +parameter +parameter EcucIntegerParamDef

DcmTimStrP2ServerAdjust: max = 255

DcmDslProtocolType: DcmDslProtocolRowUsed: EcucFloatParamDef min = 0
EcucEnumerationParamDef EcucBooleanParamDef lowerMultiplicity = 1
min = 0 upperMultiplicity = 1
lowerMultiplicity = 1 upperMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1 lowerMultiplicity = 1 upperMultiplicity = 1
symbolicNameValue = true defaultValue = true +parameter
max = 1

+parameter +parameter +subContainer

+parameter

DcmDslProtocolRow: EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 1

+parameter

DcmDslProtocolTransType: +reference +reference

EcucEnumerationParamDef
DcmDslProtocolSIDTable: DcmDslProtocolRxBufferRef:
lowerMultiplicity = 0
EcucReferenceDef EcucReferenceDef
upperMultiplicity = 1
lowerMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = 1
+literal +literal

TYPE1: TYPE2: +destination

EcucEnumerationLiteralDef EcucEnumerationLiteralDef
+subContainer DcmDslBuffer:
EcucParamConfContainerDef

+reference upperMultiplicity = 256

+parameter lowerMultiplicity = 1
DcmDemClientRef:
DcmSendRespPendOnRestart: EcucReferenceDef +destination +reference
EcucBooleanParamDef
lowerMultiplicity = 1
upperMultiplicity = 1 DcmDslProtocolTxBufferRef:
upperMultiplicity = 1
lowerMultiplicity = 1 EcucReferenceDef
defaultValue = true lowerMultiplicity = 1
upperMultiplicity = 1
+destination +destination

DemClient:
EcucParamConfContainerDef DcmDsdServiceTable:
EcucParamConfContainerDef
lowerMultiplicity = 1
upperMultiplicity = 255 upperMultiplicity = 256
lowerMultiplicity = 1

+parameter

DcmDsdSidTabId:
EcucIntegerParamDef

max = 255
min = 0
upperMultiplicity = 1
lowerMultiplicity = 1

Figure 10.10: DcmDslProtocol configuration overview

10.2.4.6 DcmDslProtocolRow

SWS Item [ECUC_Dcm_00695]

462 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Container Name DcmDslProtocolRow

Parent Container DcmDslProtocol
Description This container contains the configuration of one particular diagnostic
protocol used in Dcm.
Configuration Parameters

Name DcmDslProtocolMaximumResponseSize [ECUC_Dcm_01020]

Parent Container DcmDslProtocolRow
Description This parameter is mandatory and defines the maximum length of the
response message in case DcmPagedBufferEnabled == TRUE
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 65535
Default Value 4095
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDslProtocolPriority [ECUC_Dcm_00699]

Parent Container DcmDslProtocolRow
Description Protocol priority used during protocol preemption. A higher priority
protocol may preempt a lower priority protocol. Lower numeric values
represent higher protocol priority:

0 - Highest protocol priority

255 - Lowest protocol priority

Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

463 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDslProtocolRowUsed [ECUC_Dcm_01043]

Parent Container DcmDslProtocolRow
Description Allows to activate or deactivate the usage of a Protocol. This
parameter can be used for multi-purpose ECUs.

true - protocol is available

false - protocol is not available.

Multiplicity 1
Type EcucBooleanParamDef
Default Value true
Post-Build Variant true
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name DcmDslProtocolTransType [ECUC_Dcm_00700]

Parent Container DcmDslProtocolRow
Description This parameter is used only if the protocol is of type
DCM_ROE_ON_xxx. It selects the transmission type of the protocol.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range TYPE1 Messages on the DcmTxPduId already
used for normal diagnostic responses.
The outgoing messages must be
synchronized with ’normal outgoing
messages’, which have a higher
priority.
TYPE2 Messages on a separate DcmTxPduId.
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

464 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDslProtocolType [ECUC_Dcm_01110]

Parent Container DcmDslProtocolRow
Description The diagnostic protocol type for the DCM DSL protocol that is being
configured.

Implementation Type: Dcm_ProtocolType

Multiplicity 1
Type EcucEnumerationParamDef (Symbolic Name generated for this
parameter)
Range DCM_OBD_ON_CAN OBD on CAN (ISO15765-4;
ISO15031-5)
DCM_OBD_ON_FLEXRA
Y
DCM_OBD_ON_IP
DCM_PERIODICTRANS_
ON_CAN
DCM_PERIODICTRANS_
ON_FLEXRAY
DCM_PERIODICTRANS_
ON_IP
DCM_ROE_ON_CAN
DCM_ROE_ON_FLEXRA
Y
DCM_ROE_ON_IP
DCM_SUPPLIER_1 Reserved for SW supplier specific
DCM_SUPPLIER_10 Reserved for SW supplier specific
DCM_SUPPLIER_11 Reserved for SW supplier specific
DCM_SUPPLIER_12 Reserved for SW supplier specific
DCM_SUPPLIER_13 Reserved for SW supplier specific
DCM_SUPPLIER_14 Reserved for SW supplier specific
DCM_SUPPLIER_15 Reserved for SW supplier specific
DCM_SUPPLIER_2 Reserved for SW supplier specific
DCM_SUPPLIER_3 Reserved for SW supplier specific
DCM_SUPPLIER_4 Reserved for SW supplier specific
DCM_SUPPLIER_5 Reserved for SW supplier specific
DCM_SUPPLIER_6 Reserved for SW supplier specific
DCM_SUPPLIER_7 Reserved for SW supplier specific
DCM_SUPPLIER_8 Reserved for SW supplier specific
DCM_SUPPLIER_9 Reserved for SW supplier specific
DCM_UDS_ON_CAN UDS on CAN (ISO15765-3;
ISO14229-1)
DCM_UDS_ON_FLEXRA UDS on FlexRay (Manufacturer
Y specific; ISO14229-1)
DCM_UDS_ON_IP
DCM_UDS_ON_LIN
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –

465 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Scope / Dependency scope: ECU

Name DcmDspProtocolEcuAddr [ECUC_Dcm_01081]

Parent Container DcmDslProtocolRow
Description Ecu source address used for diagnostic communication. This
parameter is required for Generic Connections.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmSendRespPendOnRestart [ECUC_Dcm_01114]

Parent Container DcmDslProtocolRow
Description If set to TRUE, the Dcm will send a NRC 0x78 before a transition to
bootloader or performing an ECU reset. If set to False, no 0x78 is send
in this case.
Multiplicity 1
Type EcucBooleanParamDef
Default Value true
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmTimStrP2ServerAdjust [ECUC_Dcm_00729]

Parent Container DcmDslProtocolRow
Description This parameter is used to guarantee that the diagnostic response is
available on the bus before reaching P2 by adjusting the current
DcmDspSessionP2ServerMax.

This parameter mainly represents the software architecture dependent

communication delay between the time the transmission is initiated by
DCM and the time when the message is actually transmitted to the bus.

The parameter value is defined in seconds and must be a multiple of

DcmTaskTime.
Multiplicity 1
Type EcucFloatParamDef
Range [0 .. 1]

466 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmTimStrP2StarServerAdjust [ECUC_Dcm_00728]

Parent Container DcmDslProtocolRow
Description This parameter is used to guarantee that the diagnostic response is
available on the bus before reaching P2Star by adjusting the current
DcmDspSessionP2StarServerMax.

This parameter mainly represents the software architecture dependent

communication delay between the time the transmission is initiated by
DCM and the time when the message is actually transmitted to the bus.

The parameter value is defined in seconds and must be a multiple of

DcmTaskTime.
Multiplicity 1
Type EcucFloatParamDef
Range [0 .. 5]
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDemClientRef [ECUC_Dcm_01083]

Parent Container DcmDslProtocolRow
Description Reference to DemClient in Dem configuration. Used by the Dem to
distinguish different client calls.
Multiplicity 1
Type Reference to DemClient
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –

467 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDslProtocolRxBufferRef [ECUC_Dcm_00701]

Parent Container DcmDslProtocolRow
Description Reference to a configured diagnostic buffer that is used for diagnostic
request reception for the protocol.
Multiplicity 1
Type Reference to DcmDslBuffer
false
Post-Build Variant
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDslProtocolSIDTable [ECUC_Dcm_00702]

Parent Container DcmDslProtocolRow
Description Reference to a service table that is used for diagnostic request
processing for this protocol.
Multiplicity 1
Type Reference to DcmDsdServiceTable
false
Post-Build Variant
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDslProtocolTxBufferRef [ECUC_Dcm_00704]

Parent Container DcmDslProtocolRow
Description Reference to a configured diagnostic buffer that is used for diagnostic
response transmission for the protocol.
Multiplicity 1
Type Reference to DcmDslBuffer
false
Post-Build Variant
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –

468 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDslConnection 1..* This container contains the configuration of a
communication channel for one particular protocol.

Note that it is allowed to communicate with multiple

testers, therefore multiple connections may be
configured for a protocol.

469 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDslProtocolType:
+literal DCM_OBD_ON_CAN:
EcucEnumerationParamDef
EcucEnumerationLiteralDef
lowerMultiplicity = 1
upperMultiplicity = 1
+literal DCM_UDS_ON_CAN:
symbolicNameValue = true
EcucEnumerationLiteralDef

+literal DCM_UDS_ON_FLEXRAY:
EcucEnumerationLiteralDef

+literal DCM_ROE_ON_CAN:
EcucEnumerationLiteralDef

+literal DCM_ROE_ON_FLEXRAY:
EcucEnumerationLiteralDef

+literal DCM_PERIODICTRANS_ON_CAN:
EcucEnumerationLiteralDef

+literal DCM_PERIODICTRANS_ON_FLEXRAY:
EcucEnumerationLiteralDef

+literal DCM_OBD_ON_FLEXRAY:
EcucEnumerationLiteralDef

+literal DCM_ROE_ON_IP:
EcucEnumerationLiteralDef

+literal DCM_OBD_ON_IP:
EcucEnumerationLiteralDef

+literal DCM_PERIODICTRANS_ON_IP:
EcucEnumerationLiteralDef

+literal DCM_UDS_ON_IP:
EcucEnumerationLiteralDef

+literal DCM_UDS_ON_LIN:
EcucEnumerationLiteralDef

DCM_SUPPLIER_1:
+literal EcucEnumerationLiteralDef
DCM_SUPPLIER_2:
+literal EcucEnumerationLiteralDef
DCM_SUPPLIER_3:
+literal EcucEnumerationLiteralDef

DCM_SUPPLIER_4:
+literal EcucEnumerationLiteralDef
DCM_SUPPLIER_5:
+literal EcucEnumerationLiteralDef DCM_SUPPLIER_6:
+literal EcucEnumerationLiteralDef

DCM_SUPPLIER_7:
+literal EcucEnumerationLiteralDef
DCM_SUPPLIER_8:
+literal EcucEnumerationLiteralDef DCM_SUPPLIER_9:
+literal EcucEnumerationLiteralDef

DCM_SUPPLIER_10:
+literal EcucEnumerationLiteralDef
DCM_SUPPLIER_11:
+literal EcucEnumerationLiteralDef DCM_SUPPLIER_12:
+literal EcucEnumerationLiteralDef

DCM_SUPPLIER_13:
+literal EcucEnumerationLiteralDef
DCM_SUPPLIER_14:
+literal EcucEnumerationLiteralDef DCM_SUPPLIER_15:
EcucEnumerationLiteralDef
+literal

Figure 10.11: DcmDslProtocolType configuration overview

10.2.4.7 DcmDslConnection

SWS Item [ECUC_Dcm_00705]

470 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Container Name DcmDslConnection

Parent Container DcmDslProtocolRow
Description This container contains the configuration of a communication channel
for one particular protocol.

Note that it is allowed to communicate with multiple testers, therefore

multiple connections may be configured for a protocol.
Configuration Parameters

Container Choices
Container Name Multiplicity Scope / Dependency
DcmDslMainConnection 0..1 This container contains the configuration for a main
connection of a diagnostic protocol. Additionally it may
contain references to ROE and Periodic connections if
the protocol type or protocol transmission type needs
them.
DcmDslPeriodic 0..1 This container contains the configuration of a periodic
Transmission transmission connection.
DcmDslResponseOn 0..1 This container contains the configuration of a
Event ResponseOnEvent connection.

The PDU referenced by this transmission channel can

produce meta data items of type
TARGET_ADDRESS_16 and SOURCE_ADDRESS_16.

Dcm: EcucModuleDef

upperMultiplicity = 1
lowerMultiplicity = 0

DcmDsl:
EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1

+subContainer

DcmDslProtocol:
EcucParamConfContainerDef

upperMultiplicity = 1
lowerMultiplicity = 1

+subContainer

DcmDslProtocolRow:
EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 1

+subContainer

DcmDslConnection: EcucChoiceContainerDef

lowerMultiplicity = 1
upperMultiplicity = *

+choice +choice +choice

DcmDslMainConnection: DcmDslResponseOnEvent: DcmDslPeriodicTransmission:

EcucParamConfContainerDef EcucParamConfContainerDef EcucParamConfContainerDef

upperMultiplicity = 1 lowerMultiplicity = 0 lowerMultiplicity = 0

lowerMultiplicity = 0 upperMultiplicity = 1 upperMultiplicity = 1

Figure 10.12: DcmDslConnectionTable configuration overview

471 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

10.2.4.8 DcmDslMainConnection

SWS Item [ECUC_Dcm_00706]

Container Name DcmDslMainConnection
Parent Container DcmDslConnection
Description This container contains the configuration for a main connection of a
diagnostic protocol. Additionally it may contain references to ROE and
Periodic connections if the protocol type or protocol transmission type
needs them.
Configuration Parameters

Name DcmDslProtocolRxConnectionId [ECUC_Dcm_00826]

Parent Container DcmDslMainConnection
Description Unique identifier of the tester which uses this connection for diagnostic
communication.
Multiplicity 1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 0 .. 65535
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDslProtocolRxTesterSourceAddr [ECUC_Dcm_01115]

Parent Container DcmDslMainConnection
Description Tester source address uniquely describes a client and will be used e.g
within the jump to Bootloader interfaces. This parameter is not required
for generic connections (DcmPdus with MetaDataLength >= 1).
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –

472 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDslPeriodicTransmissionConRef [ECUC_Dcm_00707]

Parent Container DcmDslMainConnection
Description Reference to a periodic transmission connection which is used for the
processing of periodic transmission events.
Multiplicity 0..1
Type Reference to DcmDslPeriodicTransmission
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDslProtocolComMChannelRef [ECUC_Dcm_00952]

Parent Container DcmDslMainConnection
Description Reference to the ComMChannel on which the DcmDslProtocolRxPdu
is received and the DcmDslProtocolTxPdu is transmitted.
Multiplicity 1
Type Symbolic name reference to ComMChannel
false
Post-Build Variant
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

473 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDslROEConnectionRef [ECUC_Dcm_00708]

Parent Container DcmDslMainConnection
Description Reference to a ResponseOnEvent connection which is used for the
processing of ResponseOnEvent events.
Multiplicity 0..1
Type Reference to DcmDslResponseOnEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDslProtocolRx 1..* This container contains the configuration parameters of
a reception channel in a diagnostic connection.

The PDU referenced by this reception channel can

consume meta data items of type
SOURCE_ADDRESS_16 and TARGET_ADDRESS_16.
DcmDslProtocolTx 0..1 This container contains the configuration parameters of
a transmission channel in a diagnostic connection.

The PDU referenced by this transmission channel can

produce meta data items of type
TARGET_ADDRESS_16 and SOURCE_ADDRESS_16.

474 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDslConnection:
EcucChoiceContainerDef

lowerMultiplicity = 1
upperMultiplicity = *

+choice

DcmDslMainConnection: EcucParamConfContainerDef

upperMultiplicity = 1
lowerMultiplicity = 0

+subContainer +parameter +parameter

DcmDslProtocolTx: DcmDslProtocolRxConnectionId: DcmDslProtocolRxTesterSourceAddr:

EcucParamConfContainerDef EcucIntegerParamDef EcucIntegerParamDef

upperMultiplicity = 1 min = 0 min = 0

lowerMultiplicity = 0 max = 65535 max = 65535
lowerMultiplicity = 1 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = 1
symbolicNameValue = true
+parameter

DcmDslTxConfirmationPduId: +reference +reference

EcucIntegerParamDef
DcmDslROEConnectionRef: DcmDslPeriodicTransmissionConRef:
min = 0 EcucReferenceDef EcucReferenceDef
max = 65535
symbolicNameValue = true lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = 1

+reference
+destination +choice +destination
DcmDslProtocolTxPduRef:
EcucReferenceDef DcmDslResponseOnEvent: DcmDslPeriodicTransmission: +choice

lowerMultiplicity = 1 EcucParamConfContainerDef EcucParamConfContainerDef

upperMultiplicity = 1 lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = 1

+subContainer
+reference
DcmDslProtocolRx: EcucParamConfContainerDef

upperMultiplicity = * DcmDslProtocolComMChannelRef:
lowerMultiplicity = 1 EcucReferenceDef

lowerMultiplicity = 1
upperMultiplicity = 1
+reference requiresSymbolicNameValue = true
+parameter
+parameter
DcmDslProtocolRxPduRef: DcmDslProtocolRxPduId: +destination
EcucReferenceDef EcucIntegerParamDef DcmDslProtocolRxAddrType:
EcucEnumerationParamDef
ComMChannel:
lowerMultiplicity = 1 lowerMultiplicity = 1
lowerMultiplicity = 1 EcucParamConfContainerDef
upperMultiplicity = 1 upperMultiplicity = 1
min = 0 upperMultiplicity = 1
lowerMultiplicity = 1
symbolicNameValue = true upperMultiplicity = 256
max = 65535

+destination
+literal +literal
Pdu: EcucParamConfContainerDef
DCM_PHYSICAL_TYPE: DCM_FUNCTIONAL_TYPE:
+destination lowerMultiplicity = 0
EcucEnumerationLiteralDef EcucEnumerationLiteralDef
upperMultiplicity = *

Figure 10.13: DcmDslMainConnection configuration overview

10.2.4.9 DcmDslProtocolRx

SWS Item [ECUC_Dcm_00709]

Container Name DcmDslProtocolRx
Parent Container DcmDslMainConnection

475 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Description This container contains the configuration parameters of a reception

channel in a diagnostic connection.

The PDU referenced by this reception channel can consume meta data
items of type SOURCE_ADDRESS_16 and TARGET_ADDRESS_16.
Configuration Parameters

Name DcmDslProtocolRxAddrType [ECUC_Dcm_00710]

Parent Container DcmDslProtocolRx
Description Selects the addressing type of the reception channel. Physical
addressing is used for 1:1 communication, functional addressing is
used for 1:N communication.

For details refer to ISO 14229-1.

Multiplicity 1
Type EcucEnumerationParamDef
Range DCM_FUNCTIONAL_TYP FUNCTIONAL = 1 to n communication
E
DCM_PHYSICAL_TYPE PHYSICAL = 1 to 1 communications
using physical addressing
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDslProtocolRxPduId [ECUC_Dcm_00687]

Parent Container DcmDslProtocolRx
Description Identifier of the PDU that is used for this reception channel.
Multiplicity 1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 0 .. 65535
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

476 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDslProtocolRxPduRef [ECUC_Dcm_00770]

Parent Container DcmDslProtocolRx
Description Reference to a Pdu in EcuC that is used for this reception channel.
Multiplicity 1
Type Reference to Pdu
false
Post-Build Variant
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.4.10 DcmDslProtocolTx

SWS Item [ECUC_Dcm_00711]

Container Name DcmDslProtocolTx
Parent Container DcmDslMainConnection
Description This container contains the configuration parameters of a transmission
channel in a diagnostic connection.

The PDU referenced by this transmission channel can produce meta

data items of type TARGET_ADDRESS_16 and
SOURCE_ADDRESS_16.
Configuration Parameters

Name DcmDslTxConfirmationPduId [ECUC_Dcm_00864]

Parent Container DcmDslProtocolTx
Description Identifier of the PDU that is used by the lower level module for
transmission confirmation of responses on this channel.
Multiplicity 1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 0 .. 65535
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

477 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDslProtocolTxPduRef [ECUC_Dcm_00772]

Parent Container DcmDslProtocolTx
Description Reference to a Pdu in EcuC that is used for this transmission channel.
Multiplicity 1
Type Reference to Pdu
false
Post-Build Variant
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.4.11 DcmDslPeriodicTransmission

SWS Item [ECUC_Dcm_00741]

Container Name DcmDslPeriodicTransmission
Parent Container DcmDslConnection
Description This container contains the configuration of a periodic transmission
connection.
Configuration Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDslPeriodic 0..255 This container contains the configuration of a
Connection transmission channel for a periodic transmission
connection.

The PDU referenced by this transmission channel can

produce meta data items of type
TARGET_ADDRESS_16 and SOURCE_ADDRESS_16.

478 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDslConnection:
EcucChoiceContainerDef

lowerMultiplicity = 1
upperMultiplicity = *

+choice

DcmDslPeriodicTransmission: DcmDslPeriodicConnection:
EcucParamConfContainerDef EcucParamConfContainerDef DcmDslPeriodicTxConfirmationPduId:
EcucIntegerParamDef
lowerMultiplicity = 0 requiresIndex = true
upperMultiplicity = 1 lowerMultiplicity = 0 +parameter min = 0
upperMultiplicity = 255 max = 65535
symbolicNameValue = true
lowerMultiplicity = 1
upperMultiplicity = 1

+subContainer
DcmDslPeriodicTxPduRef:
+reference EcucReferenceDef

lowerMultiplicity = 1
upperMultiplicity = 1

+destination

Pdu: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = *

Figure 10.14: DcmDslPeriodicTransmission configuration overview

10.2.4.12 DcmDslPeriodicConnection

SWS Item [ECUC_Dcm_00897]

Container Name DcmDslPeriodicConnection
Parent Container DcmDslPeriodicTransmission
Description This container contains the configuration of a transmission channel for
a periodic transmission connection.

The PDU referenced by this transmission channel can produce meta

data items of type TARGET_ADDRESS_16 and
SOURCE_ADDRESS_16.

Attributes:
requiresIndex=true
Configuration Parameters

Name DcmDslPeriodicTxConfirmationPduId [ECUC_Dcm_00862]

Parent Container DcmDslPeriodicConnection
Description Identifier of the PDU that is used by the lower level module for
transmission confirmation of responses on this channel.
Multiplicity 1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 0 .. 65535
Default Value
Post-Build Variant false
Value

479 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDslPeriodicTxPduRef [ECUC_Dcm_00742]

Parent Container DcmDslPeriodicConnection
Description Reference to a Pdu in EcuC that is used for this periodic transmission
channel.
Multiplicity 1
Type Reference to Pdu
false
Post-Build Variant
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.4.13 DcmDslResponseOnEvent

SWS Item [ECUC_Dcm_00744]

Container Name DcmDslResponseOnEvent
Parent Container DcmDslConnection
Description This container contains the configuration of a ResponseOnEvent
connection.

The PDU referenced by this transmission channel can produce meta

data items of type TARGET_ADDRESS_16 and
SOURCE_ADDRESS_16.
Configuration Parameters

Name DcmDslRoeTxConfirmationPduId [ECUC_Dcm_00863]

Parent Container DcmDslResponseOnEvent
Description Identifier of the PDU that is used by the lower level module for
transmission confirmation of responses on this connection.
Multiplicity 0..1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 0 .. 65535
Default Value
Post-Build Variant false
Multiplicity

480 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Post-Build Variant false

Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDslRoeTxPduRef [ECUC_Dcm_00743]

Parent Container DcmDslResponseOnEvent
Description Reference to a Pdu in EcuC that is used for this ResponseOnEvent
transmission connection.
Multiplicity 0..1
Type Reference to Pdu
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers
DcmDslResponseOnEvent: DcmDslRoeTxConfirmationPduId:
EcucParamConfContainerDef EcucIntegerParamDef

lowerMultiplicity = 0 +parameter min = 0

DcmDslConnection: upperMultiplicity = 1 max = 65535
EcucChoiceContainerDef +choice symbolicNameValue = true
lowerMultiplicity = 0
lowerMultiplicity = 1 upperMultiplicity = 1
upperMultiplicity = *

DcmDslRoeTxPduRef:
+reference
EcucReferenceDef

lowerMultiplicity = 0
upperMultiplicity = 1

+destination

Pdu: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = *

Figure 10.15: DcmDslResponseOnEvent configuration overview

481 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

10.2.5 DcmDsp

SWS Item [ECUC_Dcm_00712]

Container Name DcmDsp
Parent Container DcmConfigSet
Description These parameters apply to Diagnostic Service Processing. There will
always be one set of these parameters per Dcm. Please note:
Although the multiplicity is set to 0..1. It can be expected that this
container exists in any valid DCM configuration.
Configuration Parameters

Name DcmDspDataDefaultEndianness [ECUC_Dcm_00987]

Parent Container DcmDsp
Description Defines the default endianness belonging to a DID, RID or PID if the
corresponding data does not define an endianness.
Multiplicity 1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at
the lowest address.
LITTLE_ENDIAN Most significant byte shall be stored at
the highest address
OPAQUE Opaque data endianness
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspDDDIDcheckPerSourceDID [ECUC_Dcm_00966]

Parent Container DcmDsp
Description Defines the check for session, security and mode dependencies per
source DIDs with a ReadDataByIdentifier (0x22).

true: Dcm module shall check the session, security and mode
dependencies per source DIDs with a ReadDataByIdentifier (0x22)
with DID in the range 0xF200 to 0xF3FF

false: Dcm module shall not check the session, security and mode
dependencies per source DIDs with a ReadDataByIdentifier (0x22)
with DID in the range 0xF200 to 0xF3FF
Multiplicity 0..1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value

482 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,

Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspEnableObdMirror [ECUC_Dcm_01061]

Parent Container DcmDsp
Description DcmDspEnableObdMirror defines whether a DID inside the OBD range
(F400-F4FF) and the OBD InfoType range (F800-F8FF) shall get the
DID value as defined for OBD on reception of the UDS Service
ReadDataByIdentifier (0x22), or not. It also defines whether a RID
inside the OBD range (E000-E0FF) shall handle the RID as defined for
OBD on reception of the UDS Service RoutineControl (0x31), or not.
Multiplicity 1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspMaxDidToRead [ECUC_Dcm_00638]

Parent Container DcmDsp
Description Indicates the maximum allowed DIDs in a single
"ReadDataByIdentifier" request.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 65535
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –

483 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Scope / Dependency scope: ECU

Name DcmDspMaxPeriodicDidToRead [ECUC_Dcm_00956]

Parent Container DcmDsp
Description Indicates the maximum allowed periodicDIDs which can be read in a
single "ReadDataByPeriodicIdentifier" request.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 65535
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspPowerDownTime [ECUC_Dcm_00818]

Parent Container DcmDsp
Description This parameter indicates to the client the minimum time of the stand-by
sequence the server will remain in the power-down sequence.

The resolution of this parameter is one second per count.

The following values are valid: 00 - FE hex: 0 - 254 s powerDownTime;

FF hex: indicates a failure or time not available.

This value needs to be defined by the integrator according to the ECU

capabilities. This parameter has to be available if the service
EcuReset, sub-service enableRapidPowerShutDown is configured.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –

484 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspAuthentication 0..1 This container contains the configuration for the UDS
service Authentication (0x29).
DcmDspClearDTC 0..1 This container contains the configuration for the Clear
DTC service.
DcmDspComControl 0..1 Provides the configuration of the CommunicationControl
mechanism.
DcmDspCommon 0..* This container contains the configuration (parameters)
Authorization for the common Authorization being equal for several
services / sub-services.
DcmDspControlDTC 0..1 Provide the configuration of the ControlDTCSetting
Setting mechanism.
DcmDspData 0..* This container contains the configuration (parameters)
of a Data belonging to a DID
DcmDspDataInfo 0..* This container contains the configuration (parameters)
of one Data.
DcmDspDid 0..* This container contains the configuration (parameters)
of the DID.
DcmDspDidInfo 0..* This container contains the configuration (parameters)
of the DID’s Info
DcmDspDidRange 0..* This container defines the DID Range
DcmDspEcuReset 0..1 This container contains the configuration for
DcmDspEcuReset service
DcmDspMemory 0..1 This container contains the configuration of the memory
access.
DcmDspMemoryTransfer 0..1 This container contains the configuration of the memory
transfer.
DcmDspPeriodic 0..1 This container contains the configuration (parameters)
Transmission for Periodic Transmission Scheduler.
DcmDspPid 0..* This container defines the availability of a PID to the
DCM.
DcmDspReadDTC 0..1 This container contains the configuration for the UDS
Information service ReadDTCInformation (0x19).
DcmDspRequestControl 0..* This container contains the configuration (parameters)
of the "Request control of on-board system, test or
component" service (Service $08). The DCM will
request the control using an R-Port requiring a
PortInteface RequestControlServices_{Tid}. The R-Port
is named RequestControlServices_{Tid} where {Tid} is
the name of the container DcmDspRequestControl.
DcmDspRequestFile 0..1 This container contains the configuration for
Transfer RequestFileTransfer. This container only exists if
RequestFileTransfer is configured.
DcmDspRoe 0..1 Provide the configuration of the ResponseOnEvent
mechanism.

485 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspRoutine 0..* This container contains the configuration (parameters)

for Routines
DcmDspSecurity 1 This container contains the configuration ( DSP
parameter) for security level configuration (per security
level) Description This container contains Rows of
DcmDspSecurityRow
DcmDspSession 1 Parent container holding single rows to configure
particular sessions
DcmDspVehInfo 0..* This container contains the configuration (parameters)
for one single VehicleInfoType of service $09

486 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDsp: EcucParamConfContainerDef DcmDspMaxPeriodicDidToRead:

EcucIntegerParamDef
lowerMultiplicity = 0 +parameter
upperMultiplicity = 1 lowerMultiplicity = 0
upperMultiplicity = 1
min = 1
max = 65535

DcmDspPowerDownTime:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1
min = 0
max = 255

DcmDspMaxDidToRead:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1
min = 1
max = 65535

DcmDspRoutine:
+subContainer EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

DcmDspRequestFileTransfer:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDid: EcucParamConfContainerDef
+subContainer
upperMultiplicity = *
lowerMultiplicity = 0

DcmDspDidInfo:
+subContainer EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

DcmDspSession:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspSecurity:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspPid: EcucParamConfContainerDef
+subContainer
upperMultiplicity = *
lowerMultiplicity = 0

DcmDspVehInfo:
+subContainer EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

Figure 10.16: DcmDsp configuration overview Part1

487 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDsp: EcucParamConfContainerDef DcmDspEcuReset:

+subContainer EcucParamConfContainerDef
lowerMultiplicity = 0
upperMultiplicity = 1 lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer DcmDspRequestControl:
EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

DcmDspRoe:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspComControl:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDidRange:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = *

DcmDspDDDIDcheckPerSourceDID:
+parameter EcucBooleanParamDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDataDefaultEndianness: +literal LITTLE_ENDIAN:

EcucEnumerationParamDef EcucEnumerationLiteralDef

+parameter +literal OPAQUE:

EcucEnumerationLiteralDef

+literal
BIG_ENDIAN:
EcucEnumerationLiteralDef

DcmDspClearDTC:
+subContainer EcucParamConfContainerDef

upperMultiplicity = 1
lowerMultiplicity = 0

DcmDspEnableObdMirror:
EcucBooleanParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
defaultValue = false

Figure 10.17: DcmDsp configuration overview Part2

10.2.5.1 DcmDspReadDTCInformation

SWS Item [ECUC_Dcm_01147]

Container Name DcmDspReadDTCInformation
Parent Container DcmDsp
Description This container contains the configuration for the UDS service
ReadDTCInformation (0x19).
Configuration Parameters

488 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspReadDTC 0..255 This container contains the configuration for user
InformationUserDefined defined fault memories in DcmDspReadDTCInformation.
FaultMemory

10.2.5.2 DcmDspReadDTCInformationUserDefinedFaultMemory

SWS Item [ECUC_Dcm_01148]

Container Name DcmDspReadDTCInformationUserDefinedFaultMemory
Parent Container DcmDspReadDTCInformation
Description This container contains the configuration for user defined fault
memories in DcmDspReadDTCInformation.
Configuration Parameters

Name DcmDspReadDTCInformationUserDefinedFaultMemoryId
[ECUC_Dcm_01149]
Parent Container DcmDspReadDTCInformationUserDefinedFaultMemory
Description Identifier used by external tester to identify the User defined event
Memory.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspReadDTCInformationUserDefinedFaultMemoryRole
[ECUC_Dcm_01150]
Parent Container DcmDspReadDTCInformationUserDefinedFaultMemory
Description Bitfield were each bit represents one dedicated role. A user defined
fault memory is granted access if the bit value is 1. If a bit value is 0, it
is not allowed for that role.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 4294967295
Default Value
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value

489 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Multiplicity Pre-compile time X VARIANT-PRE-COMPILE

Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

No Included Containers

10.2.5.3 DcmDspAuthentication

SWS Item [ECUC_Dcm_01151]

Container Name DcmDspAuthentication
Parent Container DcmDsp
Description This container contains the configuration for the UDS service
Authentication (0x29).
Configuration Parameters

Name DcmDspAuthenticationDeauthenticatedRole [ECUC_Dcm_01153]

Parent Container DcmDspAuthentication
Description Role used for service authentication verification in the deauthenticated
state.
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 4294967295
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationDefaultSessionTimeOut [ECUC_Dcm_01161]

Parent Container DcmDspAuthentication
Description Defines the number of seconds after which the Dcm makes a transition
to deauthenticated state, in case of no active communication.
Multiplicity 0..1
Type EcucFloatParamDef
Range [0 .. INF[

490 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationGeneralNRC [ECUC_Dcm_01159]

Parent Container DcmDspAuthentication
Description Defines the NRC that shall be send as replacement of all ISO 14229-1
defined NRCs in case of invalid certificate or content.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationRoleSize [ECUC_Dcm_01152]

Parent Container DcmDspAuthentication
Description Defines the size in bytes for the role element within a certificate.
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 4
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

491 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspAuthenticationWhiteListDIDMaxSize [ECUC_Dcm_01155]

Parent Container DcmDspAuthentication
Description Defines the maximum size in bytes for the white list element within a
certificate.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 255
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationWhiteListMemorySelectionMaxSize
[ECUC_Dcm_01157]
Parent Container DcmDspAuthentication
Description Defines the maximum size in bytes for the white list element within a
certificate.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 255
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationWhiteListRIDMaxSize [ECUC_Dcm_01156]

Parent Container DcmDspAuthentication
Description Defines the maximum size in bytes for the white list element within a
certificate.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 255
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value

492 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationWhiteListServicesMaxSize
[ECUC_Dcm_01154]
Parent Container DcmDspAuthentication
Description Defines the maximum size in bytes for the white list element within a
certificate.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 255
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationGeneralNRCModeRuleRef
[ECUC_Dcm_01158]
Parent Container DcmDspAuthentication
Description Mode rule that defines if the general NRC shall be send for all failures
due to invalid certificate or content.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

493 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspAuthenticationPersistStateModeRuleRef [ECUC_Dcm_01160]

Parent Container DcmDspAuthentication
Description References a mode rule that defines if the authentication state shall be
persisted in non-volatile memory.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspAuthentication 0..* This container contains the authentication configuration
Connection use for a dsl connection.

10.2.5.4 DcmDspAuthenticationConnection

SWS Item [ECUC_Dcm_01162]

Container Name DcmDspAuthenticationConnection
Parent Container DcmDspAuthentication
Description This container contains the authentication configuration use for a dsl
connection.
Configuration Parameters

Name DcmDspAuthenticationEcuChallengeLength [ECUC_Dcm_01186]

Parent Container DcmDspAuthenticationConnection
Description Length in byte of the ECU challenge
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 65535
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency

494 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspAuthenticationCertificatePublicKeyStoreJobRef
[ECUC_Dcm_01176]
Parent Container DcmDspAuthenticationConnection
Description Reference to a CsmJob used to store the public key within the Csm.
Multiplicity 1
Type Symbolic name reference to CsmJob
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationClientChallengeSignJobRef
[ECUC_Dcm_01174]
Parent Container DcmDspAuthenticationConnection
Description Reference to a job used to sign the client challenge.
Multiplicity 1
Type Symbolic name reference to CsmJob
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationConnectionCertificateRef [ECUC_Dcm_01164]

Parent Container DcmDspAuthenticationConnection
Description Reference to a KeyMCertificate used to store the certificate within the
KeyM.
Multiplicity 1
Type Symbolic name reference to KeyMCertificate
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value

495 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Multiplicity Pre-compile time X All Variants

Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationConnectionMainConnectionRef
[ECUC_Dcm_01163]
Parent Container DcmDspAuthenticationConnection
Description Reference to the dsl diagnostic connection that uses this
authentication configuration.
Multiplicity 1
Type Reference to DcmDslMainConnection
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationECUCertificateKeyElementRef
[ECUC_Dcm_01178]
Parent Container DcmDspAuthenticationConnection
Description Reference to a CryptoKeyElement used as server certificate during
bi-directional authentication.
Multiplicity 0..1
Type Symbolic name reference to CryptoKeyElement
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –

496 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationECUCertificateRef [ECUC_Dcm_01177]

Parent Container DcmDspAuthenticationConnection
Description Reference to a KeyMCertificate with the server certificate for
bi-directional authentication.
Multiplicity 0..1
Type Symbolic name reference to CsmKey
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationPublicKeyElementRef [ECUC_Dcm_01166]

Parent Container DcmDspAuthenticationConnection
Description Reference to a certificate data element with the public key in the
certificate.
Multiplicity 1
Type Symbolic name reference to KeyMCertificateElement
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

497 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspAuthenticationRandomJobRef [ECUC_Dcm_01173]

Parent Container DcmDspAuthenticationConnection
Description Reference to a certificate parse job used to parse the authentication
certificate.
Multiplicity 1
Type Symbolic name reference to CsmJob
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationRoleElementRef [ECUC_Dcm_01167]

Parent Container DcmDspAuthenticationConnection
Description Reference to a certificate data element with the role in the certificate.
Multiplicity 1
Type Symbolic name reference to KeyMCertificateElement
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationTargetIdentificationModeRuleRef
[ECUC_Dcm_01172]
Parent Container DcmDspAuthenticationConnection
Description Reference to a mode rule that is used to evaluate the target
identification.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value

498 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Multiplicity Pre-compile time X All Variants

Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationVerifyProofOfOwnerShipClientJobRef
[ECUC_Dcm_01175]
Parent Container DcmDspAuthenticationConnection
Description Reference to a CsmJob used to verify the proof of ownership client in
the Csm.
Multiplicity 1
Type Symbolic name reference to CsmJob
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationWhiteListDIDElementRef [ECUC_Dcm_01169]

Parent Container DcmDspAuthenticationConnection
Description Reference to a certificate data element with the white list for data
identifiers in the certificate.
Multiplicity 0..1
Type Symbolic name reference to KeyMCertificateElement
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –

499 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Scope / Dependency scope: ECU

Name DcmDspAuthenticationWhiteListMemorySelectionElementRef
[ECUC_Dcm_01171]
Parent Container DcmDspAuthenticationConnection
Description Reference to a certificate data element with the white list for user
defined memory selection in the certificate.
Multiplicity 0..1
Type Symbolic name reference to KeyMCertificateElement
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspAuthenticationWhiteListRIDElementRef [ECUC_Dcm_01170]

Parent Container DcmDspAuthenticationConnection
Description Reference to a certificate data element with the white list for routine
identifiers in the certificate.
Multiplicity 0..1
Type Symbolic name reference to KeyMCertificateElement
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

500 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspAuthenticationWhiteListServicesElementRef
[ECUC_Dcm_01168]
Parent Container DcmDspAuthenticationConnection
Description Reference to a certificate data element with the white list in the
certificate.
Multiplicity 1
Type Symbolic name reference to KeyMCertificateElement
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.5.5 Communication Control

10.2.5.5.1 DcmDspComControl

SWS Item [ECUC_Dcm_00900]

Container Name DcmDspComControl
Parent Container DcmDsp
Description Provides the configuration of the CommunicationControl mechanism.
Configuration Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspComControlAll 0..* Collection of ComM channels which shall be controlled if
Channel all networks are addressed.
DcmDspComControl 0..1 Provide the configuration of the Communication control.
Setting
DcmDspComControl 0..* Assigns subnet number to ComM channel which will be
SpecificChannel controlled.
DcmDspComControlSub 0..65535 This container gives information about the node
Node identification number and the ComM channel used to
address a sub-network.

501 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDsp:
EcucParamConfContainerDef
DcmDspAllComMChannelRef: EcucReferenceDef
lowerMultiplicity = 0
DcmDspComControlAllChannel: lowerMultiplicity = 1
upperMultiplicity = 1 +reference
EcucParamConfContainerDef upperMultiplicity = 1
requiresSymbolicNameValue = true
lowerMultiplicity = 0
upperMultiplicity = *
+subContainer

DcmDspComControl:
EcucParamConfContainerDef +subContainer +destination

lowerMultiplicity = 0 ComMChannel:
upperMultiplicity = 1 EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 256

+parameter

DcmDspComControlAllChannelUsed:
+destination
EcucBooleanParamDef

upperMultiplicity = 1 +parameter
lowerMultiplicity = 1
defaultValue = true ComMChannelId:
EcucIntegerParamDef

symbolicNameValue = true
max = 255
min = 0

DcmDspComControlSpecificChannel: DcmDspSpecificComMChannelRef:
EcucParamConfContainerDef EcucReferenceDef
+reference
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = * upperMultiplicity = 1
requiresSymbolicNameValue = true

DcmDspSubnetNumber:
+subContainer EcucIntegerParamDef
+parameter
min = 1
max = 14
lowerMultiplicity = 1
upperMultiplicity = 1

+parameter
DcmDspComControlSpecificChannelUsed:
EcucBooleanParamDef

upperMultiplicity = 1
lowerMultiplicity = 1
defaultValue = true
DcmDspComControlSetting:
EcucParamConfContainerDef
+subContainer
lowerMultiplicity = 0
upperMultiplicity = 1

+reference

DcmDspComControlCommunicationReEnableModeRuleRef: DcmModeRule:
EcucReferenceDef EcucParamConfContainerDef
+destination
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = *

Figure 10.18: DcmDspComControl configuration overview

10.2.5.5.2 DcmDspComControlAllChannel

SWS Item [ECUC_Dcm_00901]

Container Name DcmDspComControlAllChannel
Parent Container DcmDspComControl
Description Collection of ComM channels which shall be controlled if all networks
are addressed.

502 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Configuration Parameters

Name DcmDspComControlAllChannelUsed [ECUC_Dcm_01045]

Parent Container DcmDspComControlAllChannel
Description Allow to activate or deactivate the usage of a ComM channel collection
to be controlled, for multi purpose ECUs

true = ComM channel collection used false = ComM channel collection

not used
Multiplicity 1
Type EcucBooleanParamDef
Default Value true
Post-Build Variant true
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name DcmDspAllComMChannelRef [ECUC_Dcm_00902]

Parent Container DcmDspComControlAllChannel
Description Reference to ComM channel.
Multiplicity 1
Type Symbolic name reference to ComMChannel
true
Post-Build Variant
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

No Included Containers

10.2.5.5.3 DcmDspComControlSetting

SWS Item [ECUC_Dcm_00943]

Container Name DcmDspComControlSetting
Parent Container DcmDspComControl
Description Provide the configuration of the Communication control.
Configuration Parameters

503 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspComControlCommunicationReEnableModeRuleRef
[ECUC_Dcm_00944]
Parent Container DcmDspComControlSetting
Description Reference to DcmModeRule Mode rule which controls re-enabling of
communication by DCM. [ref. SWS_Dcm_00753]
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.5.5.4 DcmDspComControlSpecificChannel

SWS Item [ECUC_Dcm_00903]

Container Name DcmDspComControlSpecificChannel
Parent Container DcmDspComControl
Description Assigns subnet number to ComM channel which will be controlled.
Configuration Parameters

Name DcmDspComControlSpecificChannelUsed [ECUC_Dcm_01046]

Parent Container DcmDspComControlSpecificChannel
Description Allow to activate or deactivate the usage of a Subnet assigned to the
ComM channel which will be controlled, for multi purpose ECUs.

true = Subnet used false = Subnet not used

Multiplicity 1
Type EcucBooleanParamDef
Default Value true
Post-Build Variant true
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

504 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspSubnetNumber [ECUC_Dcm_00905]

Parent Container DcmDspComControlSpecificChannel
Description Subnet Number which controls the specific ComMChannel.
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 14
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspSpecificComMChannelRef [ECUC_Dcm_00904]

Parent Container DcmDspComControlSpecificChannel
Description Reference to ComM channel.
Multiplicity 1
Type Symbolic name reference to ComMChannel
true
Post-Build Variant
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

No Included Containers

10.2.5.5.5 DcmDspComControlSubNode

SWS Item [ECUC_Dcm_01033]

Container Name DcmDspComControlSubNode
Parent Container DcmDspComControl
Description This container gives information about the node identification number
and the ComM channel used to address a sub-network.
Configuration Parameters

505 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspComControlSubNodeId [ECUC_Dcm_01031]

Parent Container DcmDspComControlSubNode
Description The node identification number DcmDspComControlSubNodeId is
addressed by the CommunicationControl (0x28) request.
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 65535
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspComControlSubNodeUsed [ECUC_Dcm_01032]

Parent Container DcmDspComControlSubNode
Description This parameter determines if a node control function is available or not.
Multiplicity 1
Type EcucBooleanParamDef
Default Value true
Post-Build Variant true
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name DcmDspComControlSubNodeComMChannelRef [ECUC_Dcm_01030]

Parent Container DcmDspComControlSubNode
Description This parameter references a ComM channel where this node is
connected to.
Multiplicity 1
Type Symbolic name reference to ComMChannel
true
Post-Build Variant
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

506 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

No Included Containers
DcmDspComControl:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspComControlSubNode: DcmDspComControlSubNodeComMChannelRef: ComMChannel:

EcucParamConfContainerDef +reference EcucReferenceDef +destination EcucParamConfContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 1 lowerMultiplicity = 1

upperMultiplicity = 65535 upperMultiplicity = 1 upperMultiplicity = 256
requiresSymbolicNameValue = true

DcmDspComControlSubNodeId:
EcucIntegerParamDef
+parameter
max = 65535
min = 1
upperMultiplicity = 1
lowerMultiplicity = 1

DcmDspComControlSubNodeUsed:
EcucBooleanParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
defaultValue = true

Figure 10.19: DcmDspComControlSubNode configuration overview

10.2.5.6 DcmDspCommonAuthorization

SWS Item [ECUC_Dcm_01025]

Container Name DcmDspCommonAuthorization
Parent Container DcmDsp
Description This container contains the configuration (parameters) for the common
Authorization being equal for several services / sub-services.
Configuration Parameters

Name DcmDspCommonAuthorizationModeRuleRef [ECUC_Dcm_01028]

Parent Container DcmDspCommonAuthorization
Description Reference to DcmModeRule

Mode rule which controls this service/ sub-service. If there is no

reference, no check of the mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –

507 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspCommonAuthorizationSecurityLevelRef [ECUC_Dcm_01026]

Parent Container DcmDspCommonAuthorization
Description Reference to DcmDspSecurityRow Security levels allowed to control
this service/ sub-service. If there is no reference, no check of security
level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspCommonAuthorizationSessionRef [ECUC_Dcm_01027]

Parent Container DcmDspCommonAuthorization
Description Reference to DcmDspSessionRow Sessions allowed to control this
service/ sub-service. If there is no reference, no check of session level
shall be done.
Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

508 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

No Included Containers
DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspCommonAuthorization: DcmDspCommonAuthorizationSecurityLevelRef: DcmDspSecurityRow:

EcucParamConfContainerDef EcucReferenceDef EcucParamConfContainerDef
+reference +destination
upperMultiplicity = * lowerMultiplicity = 0 upperMultiplicity = 31
lowerMultiplicity = 0 upperMultiplicity = * lowerMultiplicity = 0

DcmDspCommonAuthorizationSessionRef: DcmDspSessionRow:
EcucReferenceDef EcucParamConfContainerDef
+reference +destination
lowerMultiplicity = 0 upperMultiplicity = 31
upperMultiplicity = * lowerMultiplicity = 0

DcmDspCommonAuthorizationModeRuleRef: DcmModeRule:
+reference EcucReferenceDef +destination EcucParamConfContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = *

Figure 10.20: DcmDspCommonAuthorization configuration overview

10.2.5.7 DIDs

10.2.5.7.1 DcmDspDid

SWS Item [ECUC_Dcm_00601]

Container Name DcmDspDid
Parent Container DcmDsp
Description This container contains the configuration (parameters) of the DID.
Configuration Parameters

Name DcmDspDidIdentifier [ECUC_Dcm_00602]

Parent Container DcmDspDid
Description 2 byte Identifier of the DID

Within each DcmConfigSet all DcmDspDidIdentifier values shall be

unique.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Value

509 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidSize [ECUC_Dcm_01099]

Parent Container DcmDspDid
Description Length of a DID in byte(s).
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidUsed [ECUC_Dcm_00805]

Parent Container DcmDspDid
Description Allow to activate or deactivate the usage of a DID, for multi purpose
ECUs

true = DID available false = DID not available

Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant true
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

Name DcmDspDidUsePort [ECUC_Dcm_01122]

Parent Container DcmDspDid
Description Selects application interface type for DID data elements between a
single operation for all data elements or data element specific
operations.
Multiplicity 1
Type EcucEnumerationParamDef
Range USE_ATOMIC_BNDM The DID shall be read/written from/to
BndM.

510 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

USE_ATOMIC_NV_DATA A single sender receiver interface with

_INTERFACE NvData-Ports is used for all data
elements of this DID.
USE_ATOMIC_SENDER_ A single sender receiver interface is
RECEIVER_INTERFACE used to access all data elements of
this DID. The sender receiver interface
is typed with IsService=false.
USE_ATOMIC_SENDER_ A single sender receiver interface is
RECEIVER_INTERFACE_ used to access all data elements of
AS_SERVICE this DID. The sender receiver interface
is typed with IsService=true.
USE_DATA_ELEMENT_S The data elements of this DID are
PECIFIC_INTERFACES collected by using the data element
specific interfaces defined by
DcmDspDataUsePort.
Default Value USE_DATA_ELEMENT_SPECIFIC_INTERFACES
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency

Name DcmDspDidBndMBlockIdRef [ECUC_Dcm_01185]

Parent Container DcmDspDid
Description Associate this DID with a BndM blockId.
Multiplicity 0..1
Type Symbolic name reference to BndMBlockDescriptor
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU
dependency: DcmDspDidUsePort == USE_ATOMIC_BNDM

511 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspDidInfoRef [ECUC_Dcm_00604]

Parent Container DcmDspDid
Description Reference to DcmDspDidInfo containing information on this DID.
Multiplicity 1
Type Reference to DcmDspDidInfo
false
Post-Build Variant
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidRef [ECUC_Dcm_00606]

Parent Container DcmDspDid
Description Reference to DcmDspDid in case this DID refer to one or serveral
other DID’s

Attributes:
requiresIndex=true
Multiplicity 0..*
Type Reference to DcmDspDid
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspDidSignal 0..* This container defines the reference to 1 DcmDspData
container and position relevant for this DID.
DcmDspDidSupportInfo 0..1 This container defines the support information to declare
the usability of the data bytes within the DIDs

512 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDsp:
EcucParamConfContainerDef
DcmDspData:
lowerMultiplicity = 0 EcucParamConfContainerDef
upperMultiplicity = 1 +subContainer
lowerMultiplicity = 0
upperMultiplicity = *

+destination

DcmDspDidDataRef:
EcucReferenceDef USE_ATOMIC_SENDER_RECEIVER_INTERFACE:
EcucEnumerationLiteralDef
lowerMultiplicity = 1
+reference upperMultiplicity = 1 +literal

DcmDspDidSignal:
EcucParamConfContainerDef USE_ATOMIC_NV_DATA_INTERFACE:
+parameter DcmDspDidByteOffset: EcucEnumerationLiteralDef
lowerMultiplicity = 0 EcucIntegerParamDef
upperMultiplicity = * +literal
lowerMultiplicity = 1
upperMultiplicity = 1
+subContainer USE_ATOMIC_BNDM:
+subContainer min = 0
max = 65535 EcucEnumerationLiteralDef
DcmDspDid:
EcucParamConfContainerDef +subContainer +literal
upperMultiplicity = * DcmDspDidInfoRef: DcmDspDidInfo:
lowerMultiplicity = 0 EcucReferenceDef +destination EcucParamConfContainerDef
+reference
lowerMultiplicity = 1 upperMultiplicity = *
upperMultiplicity = 1 lowerMultiplicity = 0

DcmDspDidIdentifier: DcmDspDidUsePort: EcucEnumerationParamDef

EcucIntegerParamDef
defaultValue = USE_DATA_ELEMENT_SPECIFIC_INTERFACES
+parameter lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
max = 65535
+parameter

+destination DcmDspDidRef:
+literal
EcucReferenceDef

lowerMultiplicity = 0 USE_DATA_ELEMENT_SPECIFIC_INTERFACES:
+reference upperMultiplicity = * EcucEnumerationLiteralDef
requiresIndex = true +literal

USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE:
DcmDspDidUsed: EcucEnumerationLiteralDef
+parameter EcucBooleanParamDef

upperMultiplicity = 1
lowerMultiplicity = 1 DcmDspDidSupportInfoPos:
EcucIntegerParamDef

min = 0
DcmDspDidSupportInfo: +parameter max = 255
EcucParamConfContainerDef lowerMultiplicity = 1 DcmDspDidSupportInfoLen:
+subContainer upperMultiplicity = 1 EcucIntegerParamDef
lowerMultiplicity = 0
upperMultiplicity = 1 min = 0
max = 255
+parameter lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspDidSize:
EcucIntegerParamDef
+parameter BndMBlockIdentifier: EcucIntegerParamDef
min = 0
max = 65535 min = 0
lowerMultiplicity = 0 max = 65535
upperMultiplicity = 1 symbolicNameValue = true
+parameter

DcmDspDidBndMBlockIdRef:
EcucReferenceDef BndMBlockDescriptor:
+destination EcucParamConfContainerDef
+reference lowerMultiplicity = 0
upperMultiplicity = 1 lowerMultiplicity = 0
requiresSymbolicNameValue = true upperMultiplicity = *

Figure 10.21: DcmDspDid configuration overview

10.2.5.7.2 DcmDspDidInfo

SWS Item [ECUC_Dcm_00607]

513 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Container Name DcmDspDidInfo

Parent Container DcmDsp
Description This container contains the configuration (parameters) of the DID’s Info
Configuration Parameters

Name DcmDspDDDIDMaxElements [ECUC_Dcm_00970]

Parent Container DcmDspDidInfo
Description Maximum number of source elements of a DDDID.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 255
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspDidDynamicallyDefined [ECUC_Dcm_00612]

Parent Container DcmDspDidInfo
Description Indicates if this DID can be dynamically defined

true = DID can be dynamically defined false = DID can not be

dynamically defined
Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspDidControl 0..1 This container contains the configuration (parameters)
of the DID control.
DcmDspDidRead 0..1 This container contains the configuration (parameters)
of the DID read.

514 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspDidWrite 0..1 This container contains the configuration (parameters)

of the DID write.

DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspDidInfo: DcmDspDidRead:
EcucParamConfContainerDef EcucParamConfContainerDef
+subContainer
upperMultiplicity = * upperMultiplicity = 1
lowerMultiplicity = 0 lowerMultiplicity = 0

DcmDspDidWrite:
EcucParamConfContainerDef
+subContainer
upperMultiplicity = 1
lowerMultiplicity = 0

DcmDspDidControl:
EcucParamConfContainerDef
+subContainer
upperMultiplicity = 1
lowerMultiplicity = 0

DcmDspDidDynamicallyDefined:
EcucBooleanParamDef
+parameter
upperMultiplicity = 1
lowerMultiplicity = 1

DcmDspDDDIDMaxElements:
EcucIntegerParamDef
+parameter lowerMultiplicity = 0
upperMultiplicity = 1
min = 1
max = 255

Figure 10.22: DcmDspDidInfo configuration overview

10.2.5.7.3 DcmDspDidRead

SWS Item [ECUC_Dcm_00613]

Container Name DcmDspDidRead
Parent Container DcmDspDidInfo
Description This container contains the configuration (parameters) of the DID read.
Configuration Parameters

515 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspDidReadRole [ECUC_Dcm_01141]

Parent Container DcmDspDidRead
Description Bitfield were each bit represents one dedicated role. A DID is granted
read access if the bit value is 1. If a bit value is 0, the DID is not
allowed to be read for that role.

Reading DIDs is possible by different UDS services. This setting

applies to all possible DID read operations.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 4294967295
Default Value
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

Name DcmDspDidReadModeRuleRef [ECUC_Dcm_00917]

Parent Container DcmDspDidRead
Description Reference to DcmModeRule

Mode rule which controls to read this DID. If there is no reference, no

check of the mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

516 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspDidReadSecurityLevelRef [ECUC_Dcm_00614]

Parent Container DcmDspDidRead
Description Reference to DcmDspSecurityRow Referenced security levels are
allowed to read this DID.

If there is no reference, no check of security level shall be done.

Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidReadSessionRef [ECUC_Dcm_00615]

Parent Container DcmDspDidRead
Description Reference to DcmDspSessionRow Referenced sessions are allowed to
read this DID.

If there is no reference, no check of session level shall be done.

Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

517 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

No Included Containers
DcmDspDidInfo:
EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

+subContainer

DcmDspDidRead: DcmDspDidReadSecurityLevelRef: DcmDspSecurityRow:

EcucParamConfContainerDef EcucReferenceDef EcucParamConfContainerDef
+reference +destination
upperMultiplicity = 1 lowerMultiplicity = 0 upperMultiplicity = 31
lowerMultiplicity = 0 upperMultiplicity = * lowerMultiplicity = 0

DcmDspDidReadSessionRef: EcucReferenceDef DcmDspSessionRow:

EcucParamConfContainerDef
+reference lowerMultiplicity = 0 +destination
upperMultiplicity = * upperMultiplicity = 31
lowerMultiplicity = 0

DcmDspDidReadModeRuleRef: DcmModeRule:
EcucReferenceDef EcucParamConfContainerDef
+reference +destination
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = *

DcmDspDidReadRole:
EcucIntegerParamDef
+parameter
min = 0
max = 4294967295
lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.23: DcmDspDidRead configuration overview

10.2.5.7.4 DcmDspDidSignal

SWS Item [ECUC_Dcm_00813]

Container Name DcmDspDidSignal
Parent Container DcmDspDid
Description This container defines the reference to 1 DcmDspData container and
position relevant for this DID.
Configuration Parameters

Name DcmDspDidByteOffset [ECUC_Dcm_01105]

Parent Container DcmDspDidSignal
Description Defines the absolute byte offset of the data defined by
DcmDspDidDataRef reference to DcmDspData container in the DID.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Value

518 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidDataRef [ECUC_Dcm_00808]

Parent Container DcmDspDidSignal
Description Reference to 1 DcmDspData container relevant for this DID.
Multiplicity 1
Type Reference to DcmDspData
false
Post-Build Variant
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.5.7.5 DcmDspDidSupportInfo

SWS Item [ECUC_Dcm_01102]

Container Name DcmDspDidSupportInfo
Parent Container DcmDspDid
Description This container defines the support information to declare the usability
of the data bytes within the DIDs
Configuration Parameters

Name DcmDspDidSupportInfoLen [ECUC_Dcm_01103]

Parent Container DcmDspDidSupportInfo
Description Length of the support information in bytes.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

519 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspDidSupportInfoPos [ECUC_Dcm_01100]

Parent Container DcmDspDidSupportInfo
Description Length of the support information in bytes.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.5.7.6 DcmDspDidRange

SWS Item [ECUC_Dcm_00937]

Container Name DcmDspDidRange
Parent Container DcmDsp
Description This container defines the DID Range
Configuration Parameters

Name DcmDspDidRangeHasGaps [ECUC_Dcm_00941]

Parent Container DcmDspDidRange
Description Parameter specifying if there are gaps in the DID range (parameter set
to TRUE) or not (parameter set to FALSE)
Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidRangeIdentifierLowerLimit [ECUC_Dcm_00938]

Parent Container DcmDspDidRange
Description Lower limit of DID range.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535

520 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidRangeIdentifierUpperLimit [ECUC_Dcm_00939]

Parent Container DcmDspDidRange
Description Upper limit of DID range.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidRangeIsDidAvailableFnc [ECUC_Dcm_00946]

Parent Container DcmDspDidRange
Description Function name to request from application if a specific DID is available
within the range or not. Only relevant if DcmDspDidRangeUsePort is
set to false. This parameter is related to the interface
Xxx_IsDidAvailable.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

521 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspDidRangeMaxDataLength [ECUC_Dcm_00940]

Parent Container DcmDspDidRange
Description Maximum data length in bytes
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidRangeReadDataLengthFnc [ECUC_Dcm_01067]

Parent Container DcmDspDidRange
Description Function name to request from application the length of the data of a
range DID.

Only relevant if DcmDspDidRangeUsePort is set to false. This

parameter is related to the interface Xxx_ReadDidRangeDataLength.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidRangeReadDidFnc [ECUC_Dcm_00947]

Parent Container DcmDspDidRange
Description Function name to request from application the data range value of a
DID.(ReadData-function). Only relevant if DcmDspDidRangeUsePort is
set to false. This parameter is related to the interface
Xxx_ReadDidData.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression

522 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Post-Build Variant false

Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidRangeUsePort [ECUC_Dcm_00945]

Parent Container DcmDspDidRange
Description When the parameter DcmDspDidRangeUsePort is set to true the DCM
will access the Data using an R-Port requiring a PortInteface
DataServices_DIDRange. In that case,
DcmDspDidRangeIsDidAvailableFnc, DcmDspDidRangeReadDidFnc
and DcmDspDidRangeWriteDidFnc are ignored and the RTE APIs are
used. When the parameter DcmDspDidRangeUsePort is false, the
DCM calls the functions defined in
DcmDspDidRangeIsDidAvailableFnc, DcmDspDidRangeReadDidFnc
and DcmDspDidRangeWriteDidFnc.
Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidRangeWriteDidFnc [ECUC_Dcm_00948]

Parent Container DcmDspDidRange
Description Function name to request application to write the data range value of a
DID.(WriteData-function). Only relevant if DcmDspDidRangeUsePort is
set to false. This parameter is related to the interface
Xxx_WriteDidData.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value

523 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Multiplicity Pre-compile time X All Variants

Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidRangeInfoRef [ECUC_Dcm_00950]

Parent Container DcmDspDidRange
Description Reference to DcmDspDidInfo containing information on this DID
Range.
Multiplicity 1
Type Reference to DcmDspDidInfo
false
Post-Build Variant
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

524 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

No Included Containers
DcmDspDidRange: EcucParamConfContainerDef DcmDspDidRangeIdentifierLowerLimit:
+parameter EcucIntegerParamDef
lowerMultiplicity = 0
upperMultiplicity = * min = 0
max = 65535

DcmDspDidRangeIdentifierUpperLimit:
+parameter EcucIntegerParamDef

min = 0
max = 65535

DcmDspDidRangeMaxDataLength:
+parameter EcucIntegerParamDef

min = 0
max = 65535

+parameter DcmDspDidRangeHasGaps:
EcucBooleanParamDef

+parameter DcmDspDidRangeUsePort:
EcucBooleanParamDef

DcmDspDidRangeIsDidAvailableFnc:
+parameter EcucFunctionNameDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDidRangeReadDataLengthFnc:
+parameter EcucFunctionNameDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDidRangeReadDidFnc:
+parameter EcucFunctionNameDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDidRangeWriteDidFnc:
+parameter EcucFunctionNameDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDidRangeInfoRef: DcmDspDidInfo:
+reference EcucReferenceDef +destination EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

Figure 10.24: DcmDspDidRange configuration overview

10.2.5.7.7 DcmDspDidWrite

SWS Item [ECUC_Dcm_00616]

Container Name DcmDspDidWrite
Parent Container DcmDspDidInfo
Description This container contains the configuration (parameters) of the DID write.
Configuration Parameters

525 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspDidWriteRole [ECUC_Dcm_01142]

Parent Container DcmDspDidWrite
Description Bitfield were each bit represents one dedicated role. A DID is granted
write access if the bit value is 1. If a bit value is 0, the DID is not
allowed to be written for that role.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 4294967295
Default Value
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

Name DcmDspDidWriteModeRuleRef [ECUC_Dcm_00922]

Parent Container DcmDspDidWrite
Description Reference to DcmModeRule

Mode rule which controls to write this DID. If there is no reference, no

check of the mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

526 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspDidWriteSecurityLevelRef [ECUC_Dcm_00617]

Parent Container DcmDspDidWrite
Description Reference to DcmDspSecurityRow Referenced security levels are
allowed to wirte this DID.

If there is no reference, no check of security level shall be done.

Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidWriteSessionRef [ECUC_Dcm_00618]

Parent Container DcmDspDidWrite
Description Reference to DcmDspSessionRow Referenced sessions are allowed to
write this DID.

If there is no reference, no check of session level shall be done.

Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

527 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

No Included Containers
DcmDspDidInfo:
EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

+subContainer

DcmDspDidWrite: DcmDspDidWriteSecurityLevelRef: DcmDspSecurityRow:

EcucParamConfContainerDef EcucReferenceDef EcucParamConfContainerDef
+reference +destination
upperMultiplicity = 1 lowerMultiplicity = 0 upperMultiplicity = 31
lowerMultiplicity = 0 upperMultiplicity = * lowerMultiplicity = 0

DcmDspDidWriteSessionRef: EcucReferenceDef DcmDspSessionRow:

EcucParamConfContainerDef
+reference lowerMultiplicity = 0 +destination
upperMultiplicity = * upperMultiplicity = 31
lowerMultiplicity = 0

DcmDspDidWriteModeRuleRef: DcmModeRule:
EcucReferenceDef EcucParamConfContainerDef
+reference +destination
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = *

DcmDspDidWriteRole:
EcucIntegerParamDef
+parameter
min = 0
max = 4294967295
lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.25: DcmDspDidWrite configuration overview

10.2.5.8 DcmDspControlDTCSetting

SWS Item [ECUC_Dcm_00935]

Container Name DcmDspControlDTCSetting
Parent Container DcmDsp
Description Provide the configuration of the ControlDTCSetting mechanism.
Configuration Parameters

Name DcmSupportDTCSettingControlOptionRecord [ECUC_Dcm_00965]

Parent Container DcmDspControlDTCSetting
Description This configuration switch defines if the
DTCSettingControlOptionRecord is in general supported in the request
message or not.
Multiplicity 0..1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value

528 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Multiplicity Pre-compile time X All Variants

Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspControlDTCSettingReEnableModeRuleRef
[ECUC_Dcm_00936]
Parent Container DcmDspControlDTCSetting
Description Reference to DcmModeRule

Mode rule which controls re-enabling of controlDTCsetting by DCM.

The DCM module shall execute a ControlDTCSetting.Off (call
Dem_EnableDTCSetting()) in case that the referenced mode rule is not
fulfilled anymore.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

529 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

No Included Containers
DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspControlDTCSetting: DcmDspControlDTCSettingReEnableModeRuleRef: DcmModeRule:

EcucParamConfContainerDef EcucReferenceDef +destination EcucParamConfContainerDef
+reference
lowerMultiplicity = 0 lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = 1 upperMultiplicity = *

DcmSupportDTCSettingControlOptionRecord:
+parameter EcucBooleanParamDef

upperMultiplicity = 1
lowerMultiplicity = 0
defaultValue = false

Figure 10.26: DcmDspControlDTCSetting configuration overview

10.2.5.9 Data elements

10.2.5.9.1 DcmDspData

SWS Item [ECUC_Dcm_00869]

Container Name DcmDspData
Parent Container DcmDsp
Description This container contains the configuration (parameters) of a Data
belonging to a DID
Configuration Parameters

Name DcmDspDataByteSize [ECUC_Dcm_01106]

Parent Container DcmDspData
Description Defines the array length in bytes or the the maximum array length for
variable datalengths.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –

530 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDataConditionCheckReadFnc [ECUC_Dcm_00677]

Parent Container DcmDspData
Description Function name to demand application if the conditions (e.g. System
state) to read the DID are correct. (ConditionCheckRead-function).

Multiplicity shall be equal to parameter DcmDspDataReadFnc. This

parameter is related to the interface Xxx_ConditionCheckRead.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDataConditionCheckReadFncUsed [ECUC_Dcm_00955]

Parent Container DcmDspData
Description This parameter determines if a condition check function is available or
not.
Multiplicity 0..1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –

531 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DcmDspDataEcuSignal [ECUC_Dcm_00825]

Parent Container DcmDspData
Description Function name to control the access to a certain ECU Signal by the
DCM. (IoHwAb_Dcm_<symbolic name of ECU signal>-function).
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDataEndianness [ECUC_Dcm_00986]

Parent Container DcmDspData
Description Defines the endianness of the data belonging to a DID in a diagnostic
request or response message.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at
the lowest address.
LITTLE_ENDIAN Most significant byte shall be stored at
the highest address.
OPAQUE Opaque data endianness
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –

532 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspDataFreezeCurrentStateFnc [ECUC_Dcm_00674]

Parent Container DcmDspData
Description Function name to request to application to freeze the current state of
an IOControl. (FreezeCurrentState-function).

This parameter is related to the interface Xxx_FreezeCurrentState.

Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDataGetScalingInfoFnc [ECUC_Dcm_00676]

Parent Container DcmDspData
Description Function name to request to application the scaling information of the
DID. (GetScalingInformation-function). This parameter is related to the
interface Xxxx_GetScalingInformation.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –

533 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDataReadDataLengthFnc [ECUC_Dcm_00671]

Parent Container DcmDspData
Description Function name to request from application the data length of a DID.
(ReadDataLength-function). This parameter is related to the interface
Xxx_ReadDataLength.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDataReadEcuSignal [ECUC_Dcm_00824]

Parent Container DcmDspData
Description Function name for read access to a certain ECU Signal by the DCM.
(IoHwAb_Dcm_Read<EcuSignalName>-function).

Only relevant if DcmDspDataUsePort==USE_ECU_SIGNAL.

Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –

534 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDataReadFnc [ECUC_Dcm_00669]

Parent Container DcmDspData
Description Function name to request from application the data value of a DID.
(ReadData-function). This parameter is related to the interface
Xxx_ReadData.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DcmDspDataResetToDefaultFnc [ECUC_Dcm_00673]

Parent Container DcmDspData
Description Function name to request to application to reset an IOControl to default
value. (ResetToDefault-function). This parameter is related to the
interface Xxx_ResetToDefault.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –

535 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDataReturnControlToEcuFnc [ECUC_Dcm_00672]

Parent Container DcmDspData
Description Function name to request to application to return control to ECU of an
IOControl. (ReturnControlToECU-function). This parameter is related
to the interface Xxx_ReturnControlToECU.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDataShortTermAdjustmentFnc [ECUC_Dcm_00675]

Parent Container DcmDspData
Description Function name to request to application to adjust the IO signal.
(ShortTermAdjustment-function).

This parameter is related to the interface Xxx_ShortTermAdjustment.

Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –

536 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDataType [ECUC_Dcm_00985]

Parent Container DcmDspData
Description Provide the implementation data type of data belonging to a DID.
Multiplicity 1
Type EcucEnumerationParamDef
Range BOOLEAN Type of the data is boolean.
FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 Type of the data is sint16.
SINT16_N Type of the data is sint16 array.
SINT32 Type of the data is sint32.
SINT32_N Type of the data is sint32 array.
SINT8 Type of the data is sint8.
SINT8_N Type of the data is sint8 array.
UINT16 Type of the data is uint16.
UINT16_N Type of the data is uint16 array.
UINT32 Type of the data is uint32.
UINT32_N Type of the data is uint32 array.
UINT8 Type of the data is uint8.
UINT8_DYN Type of the data is uint8 array with
dynamic length.
UINT8_N Type of the data is uint8 array.
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDataUsePort [ECUC_Dcm_00713]

Parent Container DcmDspData
Description Defines which interface shall be used to access the data.
Multiplicity 1
Type EcucEnumerationParamDef
Range USE_BLOCK_ID The DCM will access the Data using
the NVRAM Apis with the BlockId
defined in DcmDspDataBlockId

537 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

USE_DATA_ASYNCH_CL The DCM will access the Data using

IENT_SERVER an R-Port requiring a asynchronous
ClientServertInterface
DataServices_{Data}. The R-Port is
named DataServices_{Data} where
{Data} is the name of the container
DcmDspData.
USE_DATA_ASYNCH_CL The Dcm will access the Data using an
IENT_SERVER_ERROR R-Port requiring a asynchronous
ClientServertInterface
DataServices_{Data}. The parameter
ErrorCode can be returned to allow the
application to trigger a negative
response during the operation. The
R-Port is named DataServices_{Data}
where {Data} is the name of the
container DcmDspData.
USE_DATA_ASYNCH_FN The DCM will access the Data using
C the functions that are defined in
parameters of type
EcucFunctionNameDef (but without
DcmDspDataReadDataLengthFnc) in
the DcmDspData container.
DCM_E_PENDING return is allowed.
OpStatus is existing as IN parameter.
USE_DATA_ASYNCH_FN The DCM will access the Data using
C_ERROR the functions that are defined in
parameters of type
EcucFunctionNameDef (but without
DcmDspDataReadDataLengthFnc) in
the DcmDspData container.
DCM_E_PENDING return is allowed.
OpStatus is existing as IN parameter.
The parameter ErrorCode can be
returned to allow the application to
trigger a negative response during the
operation.
USE_DATA_SENDER_RE The DCM will access the Data using
CEIVER an Port requiring a
SenderReceiverInteface (with
isService=false) DataServices_{Data}.
The Port is
namedDataServices_{Data} where
{Data} is the name of the container
DcmDspData.
USE_DATA_SENDER_RE The DCM will access the Data using
CEIVER_AS_SERVICE an service Port requiring a
SenderReceiverInteface (with
isService=true) DataServices_{Data} .
The Port is
namedDataServices_{Data} where
{Data} is the name of the container
DcmDspData.

538 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

USE_DATA_SYNCH_CLI The DCM will access the Data using

ENT_SERVER an R-Port requiring a synchronous
ClientServertInterface
DataServices_{Data}.
The R-Port is named
DataServices_{Data} where {Data} is
the name of the container
DcmDspData.
USE_DATA_SYNCH_FNC The DCM will access the Data using
the functions that are defined in
parameters of type
EcucFunctionNameDef (but without
DcmDspDataReadDataLengthFnc) in
the DcmDspData container.
DCM_E_PENDING return value is not
allowed and OpStatus parameter is not
existing in the prototype.
USE_ECU_SIGNAL The DCM will access the Data using a
direct access to IoHwAb
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDataWriteFnc [ECUC_Dcm_00670]

Parent Container DcmDspData
Description Function name to request application to write the data value of a DID.
(WriteData-function). This parameter is related to the interface
Xxx_WriteData.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

539 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspOdxDataDescription [ECUC_Dcm_00988]

Parent Container DcmDspData
Description Defines additional description for ODX documentation
Multiplicity 0..1
Type EcucAddInfoParamDef
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DcmDspDataBlockIdRef [ECUC_Dcm_00809]

Parent Container DcmDspData
Description NRAM blockId to access the data.

Only relevant if DcmDspDataUsePort==USE_BLOCK_ID.

Multiplicity 0..1
Type Symbolic name reference to NvMBlockDescriptor
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDataInfoRef [ECUC_Dcm_00811]

Parent Container DcmDspData
Description Reference to 1 DcmDspDataInfo
Multiplicity 0..1
Type Reference to DcmDspDataInfo
false
Post-Build Variant
Value

540 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspDiagnosis 0..1 This container contains the configuration (parameters)
Scaling of an alternative Diagnosis Representation. Out if this
the scaling between Diagnosis and ECU internal
representation and vice versa can be calculated.
DcmDspDidDataSupport 0..1 This container defines the supported information.
Info
DcmDspExternalSRData 0..1 This container defines the source of data in a provided
ElementClass port which shall be read respectively the target of data in
a required port which shall be written.

This container shall contain either one

DcmSubElementInDataElementInstance OR
DcmDataElementInstance OR
DcmSubElementInImplDataElementInstance reference.

541 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Dcm: EcucModuleDef NvMNvramBlockIdentifier: NvMBlockDescriptor:

EcucIntegerParamDef +parameter EcucParamConfContainerDef
upperMultiplicity = 1
lowerMultiplicity = 0 symbolicNameValue = true upperMultiplicity = 65536
min = 2 lowerMultiplicity = 1
max = 65535
DcmDsp: EcucParamConfContainerDef +destination
(from Nvm)
(from Nvm)
lowerMultiplicity = 0 DcmDspDataInfo:
+subContainer EcucParamConfContainerDef DcmDspDataBlockIdRef:
upperMultiplicity = 1
EcucReferenceDef
lowerMultiplicity = 0
upperMultiplicity = * lowerMultiplicity = 0
upperMultiplicity = 1
+destination +reference requiresSymbolicNameValue = true

+subContainer DcmDspDataInfoRef: EcucReferenceDef

DcmDspDataShortTermAdjustmentFnc:
+reference lowerMultiplicity = 0 EcucFunctionNameDef
DcmDspData: upperMultiplicity = 1
EcucParamConfContainerDef lowerMultiplicity = 0
+parameter upperMultiplicity = 1
lowerMultiplicity = 0
upperMultiplicity = *
DcmDspDataReturnControlToEcuFnc:
+parameter EcucFunctionNameDef
DcmDspDataConditionCheckReadFnc:
lowerMultiplicity = 0 EcucFunctionNameDef
upperMultiplicity = 1
lowerMultiplicity = 0
+parameter
upperMultiplicity = 1

DcmDspDataResetToDefaultFnc:
+parameter EcucFunctionNameDef
DcmDspDataWriteFnc:
lowerMultiplicity = 0 EcucFunctionNameDef
upperMultiplicity = 1
lowerMultiplicity = 0
+parameter upperMultiplicity = 1

DcmDspDataByteSize:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1 DcmDspDataReadFnc:
min = 0 EcucFunctionNameDef
max = 65535 A
+parameter lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDataReadDataLengthFnc:
+parameter EcucFunctionNameDef
DcmDspDataFreezeCurrentStateFnc:
lowerMultiplicity = 0 EcucFunctionNameDef
upperMultiplicity = 1
+parameter lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDataGetScalingInfoFnc:
+parameter EcucFunctionNameDef
DcmDspDataEcuSignal:
lowerMultiplicity = 0 EcucFunctionNameDef
upperMultiplicity = 1
+parameter lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDataConditionCheckReadFncUsed:
+parameter EcucBooleanParamDef DcmDspDataReadEcuSignal:
EcucFunctionNameDef
lowerMultiplicity = 0
upperMultiplicity = 1 lowerMultiplicity = 0
+parameter
upperMultiplicity = 1

DcmDspDidDataSupportInfo: DcmDspDidDataSupportInfoBit:
+subContainer EcucParamConfContainerDef +parameter EcucIntegerParamDef

lowerMultiplicity = 0 min = 0
upperMultiplicity = 1 max = 255
lowerMultiplicity = 1
upperMultiplicity = 1

+reference
DcmDspDidSupportInfo:
DcmDspDidDataSupportInfoRef: EcucParamConfContainerDef
EcucReferenceDef +destination
lowerMultiplicity = 0
lowerMultiplicity = 1 upperMultiplicity = 1
upperMultiplicity = 1

Figure 10.27: DcmDspData1 configuration overview

542 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspData: DcmDspDataUsePort: +literal USE_DATA_SYNCH_CLIENT_SERVER:

EcucParamConfContainerDef EcucEnumerationParamDef EcucEnumerationLiteralDef

lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = * upperMultiplicity = 1 +literal
USE_DATA_ASYNCH_CLIENT_SERVER:
EcucEnumerationLiteralDef

+literal
USE_DATA_SENDER_RECEIVER:
EcucEnumerationLiteralDef

+literal
USE_DATA_SENDER_RECEIVER_AS_SERVICE:
EcucEnumerationLiteralDef

+literal
USE_DATA_SYNCH_FNC:
EcucEnumerationLiteralDef
+parameter
+literal
USE_BLOCK_ID:
EcucEnumerationLiteralDef

+literal
USE_ECU_SIGNAL:
EcucEnumerationLiteralDef

+literal USE_DATA_ASYNCH_FNC:
EcucEnumerationLiteralDef

+literal USE_DATA_ASYNCH_FNC_ERROR:
EcucEnumerationLiteralDef

+literal USE_DATA_ASYNCH_CLIENT_SERVER_ERROR:
EcucEnumerationLiteralDef

BOOLEAN:
+literal EcucEnumerationLiteralDef
DcmDspDataType:
EcucEnumerationParamDef +literal UINT8:
EcucEnumerationLiteralDef
lowerMultiplicity = 1
upperMultiplicity = 1 +literal SINT8:
EcucEnumerationLiteralDef

+literal UINT16:
EcucEnumerationLiteralDef

+literal SINT16:
EcucEnumerationLiteralDef

+literal UINT32:
EcucEnumerationLiteralDef

+literal SINT32:
EcucEnumerationLiteralDef

+parameter +literal UINT8_N:

EcucEnumerationLiteralDef
+literal SINT8_N:
EcucEnumerationLiteralDef

+literal UINT16_N:
EcucEnumerationLiteralDef

+literal SINT16_N:
EcucEnumerationLiteralDef
UINT32_N:
+literal EcucEnumerationLiteralDef

+literal SINT32_N:
EcucEnumerationLiteralDef
UINT8_DYN:
+literal EcucEnumerationLiteralDef

+literal FLOAT:
EcucEnumerationLiteralDef
FLOAT_N:
+literal EcucEnumerationLiteralDef

Figure 10.28: DcmDspData2 configuration overview

543 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspDataType: +literal BOOLEAN:

EcucEnumerationParamDef
EcucEnumerationLiteralDef

DcmDspData: lowerMultiplicity = 1
upperMultiplicity = 1 +literal UINT8:
EcucParamConfContainerDef
EcucEnumerationLiteralDef
lowerMultiplicity = 0
+literal SINT8:
upperMultiplicity = *
EcucEnumerationLiteralDef

+literal UINT16:
+parameter EcucEnumerationLiteralDef
+literal SINT16:
EcucEnumerationLiteralDef

+literal UINT32:
EcucEnumerationLiteralDef

+literal SINT32:
EcucEnumerationLiteralDef

DcmDspDataByteSize:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1
min = 0
DcmDspDataEndianness: +literal LITTLE_ENDIAN: max = 65535 A
EcucEnumerationParamDef EcucEnumerationLiteralDef
lowerMultiplicity = 0
+parameter upperMultiplicity = 1 +literal OPAQUE:
EcucEnumerationLiteralDef

+literal
BIG_ENDIAN:
EcucEnumerationLiteralDef DcmDspOdxDataDescription:
EcucAddInfoParamDef
+parameter lowerMultiplicity = 0
upperMultiplicity = 1

DcmDataElement: EcucForeignReferenceDef
DcmDspAlternativeDataInterface:
EcucParamConfContainerDef +reference lowerMultiplicity = 1
+subContainer upperMultiplicity = 1
lowerMultiplicity = 0 destinationType = VARIABLE-DATA-PROTOTYPE
+choice
DcmDspDiagnosisScaling: upperMultiplicity = 1
EcucChoiceContainerDef

lowerMultiplicity = 0 +reference DcmDspInternalDataValue:

upperMultiplicity = 1
EcucIntegerParamDef
DcmPortInterfaceMapping: EcucForeignReferenceDef
lowerMultiplicity = 1
lowerMultiplicity = 0 upperMultiplicity = 1
A
upperMultiplicity = 1
destinationType = PORT-INTERFACE-MAPPING
+parameter

DcmDspDiagnosisRepresentationDataValue:
EcucIntegerParamDef
DcmDspDiagnosticDataElementRef:
EcucForeignReferenceDef lowerMultiplicity = 1
upperMultiplicity = 1 A
lowerMultiplicity = 1
upperMultiplicity = 1
destinationType = DIAGNOSTIC-DATA-ELEMENT +parameter

+reference
DcmDspAlternativeDataType: DcmDspTextTableMapping:
EcucParamConfContainerDef +subContainer EcucParamConfContainerDef
+choice
lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = *

+choice
+reference
DcmDspAlternativeDiagnosticDataElement:
EcucParamConfContainerDef
DcmApplicationDataType:
lowerMultiplicity = 0 EcucForeignReferenceDef
upperMultiplicity = 1
lowerMultiplicity = 1
upperMultiplicity = 1
destinationType = APPLICATION-DATA-TYPE

Figure 10.29: DcmDspSRData1 configuration overview

544 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspData: DcmDspExternalSRDataElementClass:
EcucParamConfContainerDef EcucChoiceContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = 1
+subContainer

DcmSubElementInDataElementInstance:
+choice EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+choice +choice

DcmDataElementInstance: DcmSubElementInImplDataElementInstance:
EcucParamConfContainerDef EcucParamConfContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = 1

+reference

DcmDataElementInstanceRef: EcucInstanceReferenceDef

lowerMultiplicity = 1
upperMultiplicity = 1
destinationContext = ROOT-SW-COMPOSITION-PROTOTYPE SW-COMPONENT-PROTOTYPE PORT-PROTOTYPE
destinationType = AUTOSAR-DATA-PROTOTYPE

             

       

 !   "   

+reference

DcmSubElementInImplDataElementInstanceRef: EcucInstanceReferenceDef

             

       

 !   "   

+reference

DcmSubElementInDataElementInstanceRef: EcucInstanceReferenceDef

Figure 10.30: DcmDspSRData2 configuration overview

10.2.5.9.2 DcmDspDiagnosisScaling

SWS Item [ECUC_Dcm_00993]

Container Name DcmDspDiagnosisScaling
Parent Container DcmDspData, DcmDspPidService01
Description This container contains the configuration (parameters) of an alternative
Diagnosis Representation. Out if this the scaling between Diagnosis
and ECU internal representation and vice versa can be calculated.
Configuration Parameters

545 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Container Choices
Container Name Multiplicity Scope / Dependency
DcmDspAlternativeData 0..1 This container contains the configuration (parameters)
Interface of an alternative Diagnosis Representation by the
means of a VariableDataPrototoype in a DataInterface.

Additionally a reference to PortInterfaceMapping can be

defined which provide already the mapping rules
between the VariableDataPrototoype in a DataInterface
used by the software component
(DcmDspExternalSRDataElementClass) and the
intended Diagnosis Representation defined by
DcmDataElement.
DcmDspAlternativeData 0..1 This container contains the configuration (parameters)
Type of an alternative Diagnosis Representation by the
means of an ApplicationDataType.

Additionally the definition of a text table mapping can be

a defined for ApplicationDataTypes with a
CompuMethod of category TEXTTABLE and
SCALE_LINEAR_AND_TEXTTABLE.
DcmDspAlternative 0..1 This container contains the configuration (parameters)
DiagnosticDataElement of an alternative Diagnosis Representation by the
means of Diagnostic Extract.

10.2.5.9.3 DcmDspArgumentScaling

SWS Item [ECUC_Dcm_01062]

Container Name DcmDspArgumentScaling
Parent Container DcmDspRequestRoutineResultsInSignal, DcmDspRequestRoutine
ResultsOutSignal, DcmDspStartRoutineInSignal, DcmDspStartRoutine
OutSignal, DcmDspStopRoutineInSignal, DcmDspStopRoutineOut
Signal
Description This container contains the configuration (arguments) of an alternative
Diagnosis Representation. Out if this the scaling between Diagnosis
and ECU internal representation and vice versa can be calculated.
Configuration Parameters

Container Choices
Container Name Multiplicity Scope / Dependency
DcmDspAlternative 0..1 This container contains the configuration (parameters)
ArgumentData of an alternative Diagnosis Representation by the
means of a ArgumentDataPrototype.
DcmDspAlternativeData 0..1 This container contains the configuration (parameters)
Type of an alternative Diagnosis Representation by the
means of an ApplicationDataType.

Additionally the definition of a text table mapping can be

a defined for ApplicationDataTypes with a
CompuMethod of category TEXTTABLE and
SCALE_LINEAR_AND_TEXTTABLE.

546 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspAlternative 0..1 This container contains the configuration (parameters)

DiagnosticDataElement of an alternative Diagnosis Representation by the
means of Diagnostic Extract.

DcmDspStartRoutineInSignal: DcmDspArgumentScaling:
EcucParamConfContainerDef EcucChoiceContainerDef
+subContainer
upperMultiplicity = * lowerMultiplicity = 0
lowerMultiplicity = 1 upperMultiplicity = 1
requiresIndex = true

DcmDspStartRoutineOutSignal: DcmDspAlternativeArgumentData:
EcucParamConfContainerDef EcucParamConfContainerDef
+choice
+subContainer
upperMultiplicity = * lowerMultiplicity = 0
lowerMultiplicity = 1 upperMultiplicity = 1
requiresIndex = true

DcmDspStopRoutineInSignal: +reference
EcucParamConfContainerDef
+subContainer DcmDataElement: EcucForeignReferenceDef
upperMultiplicity = *
lowerMultiplicity = 1
lowerMultiplicity = 1
upperMultiplicity = 1
requiresIndex = true
destinationType = ARGUMENT-DATA-PROTOTYPE

DcmDspStopRoutineOutSignal:
EcucParamConfContainerDef DcmDspAlternativeDataType:
+subContainer
+choice EcucParamConfContainerDef
upperMultiplicity = *
lowerMultiplicity = 1 lowerMultiplicity = 0
requiresIndex = true upperMultiplicity = 1

DcmDspRequestRoutineResultsInSignal: DcmDspAlternativeDiagnosticDataElement:
EcucParamConfContainerDef EcucParamConfContainerDef
+subContainer +choice
upperMultiplicity = * lowerMultiplicity = 0
lowerMultiplicity = 1 upperMultiplicity = 1
requiresIndex = true

DcmDspRequestRoutineResultsOutSignal:
EcucParamConfContainerDef +reference
+subContainer
upperMultiplicity = * DcmDspDiagnosticDataElementRef:
lowerMultiplicity = 1 EcucForeignReferenceDef
requiresIndex = true
lowerMultiplicity = 1
upperMultiplicity = 1
destinationType = DIAGNOSTIC-DATA-ELEMENT

Figure 10.31: DcmDspArgumentScaling configuration overview

10.2.5.9.4 DcmDspAlternativeArgumentData

SWS Item [ECUC_Dcm_01055]

Container Name DcmDspAlternativeArgumentData
Parent Container DcmDspArgumentScaling
Description This container contains the configuration (parameters) of an alternative
Diagnosis Representation by the means of a ArgumentDataPrototype.
Configuration Parameters

547 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDataElement [ECUC_Dcm_01056]

Parent Container DcmDspAlternativeArgumentData
Description Alternative Diagnosis Representation for the data defined by the
means of a ArgumentDataPrototype.

The CompuMethod of the data type of the referenced

ArgumentDataPrototype will be applied to the data type of the
ArgumentDataPrototype in the interface used by the Dcm.
Multiplicity 1
Type Foreign reference to ARGUMENT-DATA-PROTOTYPE
false
Post-Build Variant
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency

No Included Containers

10.2.5.9.5 DcmDspTextTableMapping

SWS Item [ECUC_Dcm_00999]

Container Name DcmDspTextTableMapping
Parent Container DcmDspAlternativeDataType
Description The purpose of the DcmDspTextTableMapping is to associate a
texttable value defined in the context of the Dcm to a texttable value
defined in the context of a CompuMethod referenced by a DataType
that shall be taken to create a dataElement in a
SenderReceiverInterface. By this means it is possible to create a
primitive version of a TexttableMapping (which can only be applied if a
dataElement already exists).

In other words, the DcmDspTextTableMapping provides a similar

mechanism to the TexttableMapping in a situation where the
TexttableMapping cannot be applied since the
SenderReceiverInterface for the PortPrototype on the Dcm
ServiceComponent does not yet exist.
Configuration Parameters

Name DcmDspDiagnosisRepresentationDataValue [ECUC_Dcm_01001]

Parent Container DcmDspTextTableMapping
Description The data value in the diagnosis representation.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 ..
18446744073709551615
Default Value

548 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Post-Build Variant false

Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspInternalDataValue [ECUC_Dcm_01000]

Parent Container DcmDspTextTableMapping
Description The ECU internal data value.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 ..
18446744073709551615
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.5.9.6 DcmDspAlternativeDataInterface

SWS Item [ECUC_Dcm_00994]

Container Name DcmDspAlternativeDataInterface
Parent Container DcmDspDiagnosisScaling
Description This container contains the configuration (parameters) of an alternative
Diagnosis Representation by the means of a VariableDataPrototoype in
a DataInterface.

Additionally a reference to PortInterfaceMapping can be defined which

provide already the mapping rules between the
VariableDataPrototoype in a DataInterface used by the software
component (DcmDspExternalSRDataElementClass) and the intended
Diagnosis Representation defined by DcmDataElement.
Configuration Parameters

549 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDataElement [ECUC_Dcm_00995]

Parent Container DcmDspAlternativeDataInterface
Description Alternative Diagnosis Representation for the data defined by the
means of a VariableDataPrototoype in a DataInterface.

The CompuMethod of the data type of the referenced

VariableDataPrototype will be applied to the data type of the
VariableDataPrototype in the interface used by the Dcm.
Multiplicity 1
Type Foreign reference to VARIABLE-DATA-PROTOTYPE
false
Post-Build Variant
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency

Name DcmPortInterfaceMapping [ECUC_Dcm_00996]

Parent Container DcmDspAlternativeDataInterface
Description Optional reference to PortInterfaceMapping which defines the mapping
rules.

The PortInterfaceMapping is used to get the DataPrototypeMapping

that describes a conversion between the data prototype referenced by
DcmDataElement and the data prototype referenced from
DcmDspExternalSRDataElementClass.
Multiplicity 0..1
Type Foreign reference to PORT-INTERFACE-MAPPING
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency

No Included Containers

10.2.5.9.7 DcmDspAlternativeDataType

550 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

SWS Item [ECUC_Dcm_00997]

Container Name DcmDspAlternativeDataType
Parent Container DcmDspArgumentScaling, DcmDspDiagnosisScaling
Description This container contains the configuration (parameters) of an alternative
Diagnosis Representation by the means of an ApplicationDataType.

Additionally the definition of a text table mapping can be a defined for

ApplicationDataTypes with a CompuMethod of category TEXTTABLE
and SCALE_LINEAR_AND_TEXTTABLE.
Configuration Parameters

Name DcmApplicationDataType [ECUC_Dcm_00998]

Parent Container DcmDspAlternativeDataType
Description Alternative Diagnosis Representation for the data defined by the means
of a ApplicationDataType of category VALUE, BOOLEAN or ARRAY.

The CompuMethod that applies to the referenced ApplicationDataType

in case of category VALUE or BOOLEAN will be applied to the data
type of the VariableDataPrototype in the interface used by the Dcm.
Multiplicity 1
Type Foreign reference to APPLICATION-DATA-TYPE
false
Post-Build Variant
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspTextTable 0..* The purpose of the DcmDspTextTableMapping is to
Mapping associate a texttable value defined in the context of the
Dcm to a texttable value defined in the context of a
CompuMethod referenced by a DataType that shall be
taken to create a dataElement in a
SenderReceiverInterface. By this means it is possible to
create a primitive version of a TexttableMapping (which
can only be applied if a dataElement already exists).

In other words, the DcmDspTextTableMapping provides

a similar mechanism to the TexttableMapping in a
situation where the TexttableMapping cannot be applied
since the SenderReceiverInterface for the PortPrototype
on the Dcm ServiceComponent does not yet exist.

10.2.5.9.8 DcmDspAlternativeDiagnosticDataElement

SWS Item [ECUC_Dcm_01084]

551 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Container Name DcmDspAlternativeDiagnosticDataElement

Parent Container DcmDspArgumentScaling, DcmDspDiagnosisScaling
Description This container contains the configuration (parameters) of an alternative
Diagnosis Representation by the means of Diagnostic Extract.
Configuration Parameters

Name DcmDspDiagnosticDataElementRef [ECUC_Dcm_01085]

Parent Container DcmDspAlternativeDiagnosticDataElement
Description Alternative Diagnosis Representation for the data defined by the
means of a DiagnosticDataElement in the Diagnostic Extract.

This EcucForeignReference enables the access to all

SwDataDefProps, in particular BaseType, CompuMethod and
DataConstr

The CompuMethod and DataConstr that applies to the referenced

DiagnosticDataElement will be applied to the data type of the
VariableDataPrototype in the interface used by the Dcm. The mapped
ImplementationDataType needs to match the given BaseType.
Multiplicity 1
Type Foreign reference to DIAGNOSTIC-DATA-ELEMENT
false
Post-Build Variant
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

No Included Containers

10.2.5.9.9 DcmDataElementInstance

SWS Item [ECUC_Dcm_01010]

Container Name DcmDataElementInstance
Parent Container DcmDspExternalSRDataElementClass, DcmDspPidService01External
SRDataElementClass
Description Instance Reference to the primitive data in a port where the data
element is typed with an ApplicationPrimitveDataType or an
ImplementationDataType.
Configuration Parameters

552 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDataElementInstanceRef [ECUC_Dcm_00991]

Parent Container DcmDataElementInstance
Description Instance Reference to the primitive or array data which shall be read or
written. Supported are VariableDataPrototypes in
SenderReceiverInterfaces and NvDataInterfaces and
ParameterDataPrototypes in ParameterInterfaces (read only). This
reference is applicable if the AutosarDataPrototype is typed with a
ApplicationPrimitiveDataType of category VALUE or BOOLEAN or
ApplicationArrayDataType or if the AutosarDataPrototype is typed with
a ImplementationDataType of category VALUE, ARRAY or
TYPE_REFERENCE that in turn boils down to VALUE or ARRAY
Multiplicity 1
Type Instance reference to AUTOSAR-DATA-PROTOTYPE context: ROOT-
SW-COMPOSITION-PROTOTYPE SW-COMPONENT-PROTOTYPE
PORT-PROTOTYPE
false
Post-Build Variant
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency

No Included Containers

10.2.5.9.10 DcmDspExternalSRDataElementClass

SWS Item [ECUC_Dcm_00989]

Container Name DcmDspExternalSRDataElementClass
Parent Container DcmDspData
Description This container defines the source of data in a provided port which shall
be read respectively the target of data in a required port which shall be
written.

This container shall contain either one

DcmSubElementInDataElementInstance OR
DcmDataElementInstance OR
DcmSubElementInImplDataElementInstance reference.
Configuration Parameters

Container Choices
Container Name Multiplicity Scope / Dependency
DcmDataElement 0..1 Instance Reference to the primitive data in a port where
Instance the data element is typed with an
ApplicationPrimitveDataType or an
ImplementationDataType.

553 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmSubElementInData 0..1 Instance Reference to the primitve sub-element (at any

ElementInstance level) of composite data in a port where the data element
is typed with an ApplicationCompositeDataType.
DcmSubElementInImpl 0..1 Instance Reference to the primitve sub-element (at any
DataElementInstance level) of composite data in a port where the data
element is typed with an ImplementationDataType.

10.2.5.9.11 DcmSubElementInDataElementInstance

SWS Item [ECUC_Dcm_01009]

Container Name DcmSubElementInDataElementInstance
Parent Container DcmDspExternalSRDataElementClass, DcmDspPidService01External
SRDataElementClass
Description Instance Reference to the primitve sub-element (at any level) of
composite data in a port where the data element is typed with an
ApplicationCompositeDataType.
Configuration Parameters

Name DcmSubElementInDataElementInstanceRef [ECUC_Dcm_00990]

Parent Container DcmSubElementInDataElementInstance
Description Instance Reference to the primitve sub-element (at any level) of
composite data in a port which shall be read. Supported are
VariableDataPrototypes in SenderReceiverInterfaces and
NvDataInterfaces and ParameterDataPrototypes in
ParameterInterfaces (read only). This reference is applicable if the
AutosarDataPrototype is typed with a ApplicationCompositeDataType.

Note: One or more class attributes are too long to display. Please refer
to diagram INTERNAL_DcmDspSRData for the class attributes.
Multiplicity 1
Type Instance reference to APPLICATION-COMPOSITE-ELEMENT-DATA-
PROTOTYPE context: ROOT-SW-COMPOSITION-PROTOTYPE SW-
COMPONENT-PROTOTYPE PORT-PROTOTYPE AUTOSAR-DATA-P
ROTOTYPE APPLICATION-COMPOSITE-ELEMENT-DATA-PROTOT
YPE*
false
Post-Build Variant
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency

No Included Containers

554 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

10.2.5.9.12 DcmSubElementInImplDataElementInstance

SWS Item [ECUC_Dcm_01011]

Container Name DcmSubElementInImplDataElementInstance
Parent Container DcmDspExternalSRDataElementClass, DcmDspPidService01External
SRDataElementClass
Description Instance Reference to the primitve sub-element (at any level) of
composite data in a port where the data element is typed with an
ImplementationDataType.
Configuration Parameters

Name DcmSubElementInImplDataElementInstanceRef [ECUC_Dcm_00992]

Parent Container DcmSubElementInImplDataElementInstance
Description Instance Reference to the primitve sub-element (at any level) of
composite data in a port which shall be read. Supported are
VariableDataPrototypes in SenderReceiverInterfaces and
NvDataInterfaces and ParameterDataPrototypes in
ParameterInterfaces (read only). This reference is applicable if the
AutosarDataPrototype is typed with a ImplementationDataType of
category STRUCTURE or ARRAY. Please note that in case of ARRAY
the index attribute in the target reference has to be set to select a
single array element.

Note: One or more class attributes are too long to display. Please refer
to diagram INTERNAL_DcmDspSRData for the class attributes.
Multiplicity 1
Type Instance reference to IMPLEMENTATION-DATA-TYPE-ELEMENT
context: ROOT-SW-COMPOSITION-PROTOTYPE SW-COMPONENT-
PROTOTYPE PORT-PROTOTYPE AUTOSAR-DATA-PROTOTYPE I
MPLEMENTATION-DATA-TYPE-ELEMENT*
false
Post-Build Variant
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency

No Included Containers

10.2.5.9.13 DcmDspDidDataSupportInfo

SWS Item [ECUC_Dcm_01104]

Container Name DcmDspDidDataSupportInfo
Parent Container DcmDspData
Description This container defines the supported information.
Configuration Parameters

555 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspDidDataSupportInfoBit [ECUC_Dcm_01097]

Parent Container DcmDspDidDataSupportInfo
Description Referenced Bit of the SupportInfo
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidDataSupportInfoRef [ECUC_Dcm_01098]

Parent Container DcmDspDidDataSupportInfo
Description Reference to DcmDspDidSupportInfo
Multiplicity 1
Type Reference to DcmDspDidSupportInfo
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.5.9.14 DcmDspDataInfo

SWS Item [ECUC_Dcm_00810]

Container Name DcmDspDataInfo
Parent Container DcmDsp
Description This container contains the configuration (parameters) of one Data.
Configuration Parameters

556 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspDataScalingInfoSize [ECUC_Dcm_00611]

Parent Container DcmDspDataInfo
Description If Scaling information service is available for this Data, it provides the
size in bytes of the scaling information.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 4294967295
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers
DcmConfigSet:
EcucParamConfContainerDef

+subContainer

DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspDataInfo: DcmDspDataScalingInfoSize:
EcucParamConfContainerDef EcucIntegerParamDef
+parameter
lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = 1
min = 0
max = 4294967295

Figure 10.32: DcmDspDataInfo configuration overview

10.2.5.10 DcmDspDidControl

SWS Item [ECUC_Dcm_00619]

Container Name DcmDspDidControl
Parent Container DcmDspDidInfo
Description This container contains the configuration (parameters) of the DID
control.
Configuration Parameters

557 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspDidControlMask [ECUC_Dcm_01059]

Parent Container DcmDspDidControl
Description This indicates the presence of "controlEnableMask" in SWC service
interfaces and defines how the Dcm treats a service request.
Multiplicity 1
Type EcucEnumerationParamDef
Range DCM_CONTROLMASK_E The control enable mask record shall
XTERNAL be forwarded within each interface and
is handled externally.
DCM_CONTROLMASK_I The control enable mask record is
NTERNAL handled internally and Dcm controls
only the included signals.
DCM_CONTROLMASK_N No control enable mask handling.
O
Default Value DCM_CONTROLMASK_INTERNAL
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidControlMaskSize [ECUC_Dcm_01060]

Parent Container DcmDspDidControl
Description The value defines the size of the controlEnableMaskRecord in bytes.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 4294967294
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidControlRole [ECUC_Dcm_01143]

Parent Container DcmDspDidControl
Description Bitfield were each bit represents one dedicated role. A DID is granted
IOcontrol access if the bit value is 1. If a bit value is 0, the DID is not
allowed to be controlled for that role.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 4294967295
Default Value
Post-Build Variant true
Multiplicity

558 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Post-Build Variant true

Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

Name DcmDspDidFreezeCurrentState [ECUC_Dcm_00624]

Parent Container DcmDspDidControl
Description This indicates the presence of "FreezeCurrentState".
Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidResetToDefault [ECUC_Dcm_00623]

Parent Container DcmDspDidControl
Description This indicates the presence of "ResetToDefault".
Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidShortTermAdjustment [ECUC_Dcm_00625]

Parent Container DcmDspDidControl
Description This indicates the presence of "ShortTermAdjustment".
Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Value

559 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidControlModeRuleRef [ECUC_Dcm_00923]

Parent Container DcmDspDidControl
Description Reference to DcmModeRule

Mode rule which controls this DID. If there is no reference, no check of

the mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspDidControlSecurityLevelRef [ECUC_Dcm_00620]

Parent Container DcmDspDidControl
Description Reference to DcmDspSecurityRow Security levels allowed to control
this DID. If there is no reference, no check of security level shall be
done.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

560 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspDidControlSessionRef [ECUC_Dcm_00621]

Parent Container DcmDspDidControl
Description Reference to DcmDspSessionRow Sessions allowed to control this
DID. If there is no reference, no check of session level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspDidControl 0..32 The shortname of the container value defines the
EnableMask symbol of the controlMask.

561 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspDidInfo:
EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

+subContainer

DcmDspDidControl: DcmDspDidControlSecurityLevelRef: DcmDspSecurityRow:

EcucParamConfContainerDef EcucReferenceDef EcucParamConfContainerDef
+reference +destination
upperMultiplicity = 1 lowerMultiplicity = 0 upperMultiplicity = 31
lowerMultiplicity = 0 upperMultiplicity = * lowerMultiplicity = 0

DcmDspDidControlSessionRef: DcmDspSessionRow:
EcucReferenceDef EcucParamConfContainerDef
+reference +destination
lowerMultiplicity = 0 upperMultiplicity = 31
upperMultiplicity = * lowerMultiplicity = 0

DcmDspDidResetToDefault:
EcucBooleanParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspDidFreezeCurrentState:
EcucBooleanParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1 DcmDspDidControlRole:
EcucIntegerParamDef
+parameter
min = 0
max = 4294967295
DcmDspDidShortTermAdjustment: lowerMultiplicity = 0
+parameter EcucBooleanParamDef upperMultiplicity = 1

lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspDidControlMaskBitPosition: EcucIntegerParamDe

DcmDspDidControlEnableMask: lowerMultiplicity = 1
+subContainer EcucParamConfContainerDef upperMultiplicity = 1
+parameter min = 0
upperMultiplicity = 32 max = 31
lowerMultiplicity = 0

DcmDspDidControlMask: EcucEnumerationParamDef +literal DCM_CONTROLMASK_INTERNAL:

EcucEnumerationLiteralDef
lowerMultiplicity = 1
upperMultiplicity = 1
defaultValue = DCM_CONTROLMASK_INTERNAL
+parameter +literal DCM_CONTROLMASK_EXTERNAL:
EcucEnumerationLiteralDef

+literal DCM_CONTROLMASK_NO:
EcucEnumerationLiteralDef

DcmDspDidControlMaskSize: EcucIntegerParamDef

lowerMultiplicity = 0
upperMultiplicity = 1
min = 1
+parameter max = 4294967294

Figure 10.33: DcmDspDidControl configuration overview

562 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

10.2.5.11 DcmDspDidControlEnableMask

SWS Item [ECUC_Dcm_01057]

Container Name DcmDspDidControlEnableMask
Parent Container DcmDspDidControl
Description The shortname of the container value defines the symbol of the
controlMask.
Configuration Parameters

Name DcmDspDidControlMaskBitPosition [ECUC_Dcm_01058]

Parent Container DcmDspDidControlEnableMask
Description Defines the position of the bit in the controlMask starting. The counting
order is from the most significant bit (MSB first) to least significant bit.
A value of 0 identifies the most significant bit in the MSB of the control
enable mask. A value of 0 represents also the first controlState
parameter. The bit endianness is identical to the controlMask in UDS.
The number of possible and available bits is given by
DcmDspDidControlMaskSize.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 31
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.5.12 Ecu Reset

10.2.5.12.1 DcmDspEcuReset

SWS Item [ECUC_Dcm_01111]

Container Name DcmDspEcuReset
Parent Container DcmDsp
Description This container contains the configuration for DcmDspEcuReset service
Configuration Parameters

563 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspEcuResetRow 1..* This container contains the configuration for each
DcmDspEcuReset subservice.

DcmDsp:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspEcuReset:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspEcuResetRow: DcmDspEcuResetId:
EcucParamConfContainerDef EcucIntegerParamDef

lowerMultiplicity = 1 +parameter
min = 0
upperMultiplicity = * max = 127
lowerMultiplicity = 1
upperMultiplicity = 1

DcmResponseToEcuReset: +literal BEFORE_RESET:

EcucEnumerationParamDef EcucEnumerationLiteralDef
+parameter lowerMultiplicity = 1
upperMultiplicity = 1
+literal AFTER_RESET:
EcucEnumerationLiteralDef

Figure 10.34: DcmDspEcuReset configuration overview

10.2.5.12.2 DcmDspEcuResetRow

SWS Item [ECUC_Dcm_01112]

Container Name DcmDspEcuResetRow
Parent Container DcmDspEcuReset
Description This container contains the configuration for each DcmDspEcuReset
subservice.
Configuration Parameters

Name DcmDspEcuResetId [ECUC_Dcm_01113]

Parent Container DcmDspEcuResetRow
Description Defines the subfunction ID
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 127
Default Value
Post-Build Variant false
Multiplicity

564 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Post-Build Variant false

Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmResponseToEcuReset [ECUC_Dcm_01039]

Parent Container DcmDspEcuResetRow
Description Defines the answer to EcuReset service should come: Before or after
the reset.
Multiplicity 1
Type EcucEnumerationParamDef
Range AFTER_RESET Answer to EcuReset service should
come after the reset.
BEFORE_RESET Answer to EcuReset service should
come before the reset.
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.5.13 Memory

10.2.5.13.1 DcmDspMemory

SWS Item [ECUC_Dcm_00784]

Container Name DcmDspMemory
Parent Container DcmDsp
Description This container contains the configuration of the memory access.
Configuration Parameters

565 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspAddressAnd 0..1 This container contains the configuration of the
LengthFormatIdentifier supported AddressAndLengthFormatIdentifiers for
memory access.
DcmDspMemoryIdInfo 1..* Provides the value of memory identifier used to select
the desired memory device

This container contains the configuration of the memory

access requested through diagnostic services :
ReadMemoryByAddress, WriteMemoryByAddress, and
DynamicallyDefineDataIdentifier

10.2.5.13.2 DcmDspMemoryTransfer

SWS Item [ECUC_Dcm_01132]

Container Name DcmDspMemoryTransfer
Parent Container DcmDsp
Description This container contains the configuration of the memory transfer.
Configuration Parameters

Name DcmDspMemoryTransferFnc [ECUC_Dcm_01134]

Parent Container DcmDspMemoryTransfer
Description Function name for memory transfer services. Only relevant if
DcmDspMemoryTransferUsePort is set to false.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

566 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspMemoryTransferUsePort [ECUC_Dcm_01133]

Parent Container DcmDspMemoryTransfer
Description If this parameter is set to true, the Dcm uses a port requiring a
PortInterface UploadDownload. If the parameter is false, the DCM
uses the according C-API callouts.
Multiplicity 1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspAddressAnd 0..1 This container contains the configuration of the
LengthFormatIdentifier supported AddressAndLengthFormatIdentifiers for
memory access.
DcmDspMemoryTransfer 1..* Provides the value of memory identifier used to select
IdInfo the desired memory device

This container contains the configuration of the memory

access requested through diagnostic services :
RequestDownload, RequestUpload, TransferData,
RequestTransferExit

10.2.5.13.3 DcmDspAddressAndLengthFormatIdentifier

SWS Item [ECUC_Dcm_00963]

Container Name DcmDspAddressAndLengthFormatIdentifier
Parent Container DcmDspMemory, DcmDspMemoryTransfer
Description This container contains the configuration of the supported
AddressAndLengthFormatIdentifiers for memory access.
Configuration Parameters

Name DcmDspSupportedAddressAndLengthFormatIdentifier
[ECUC_Dcm_00964]
Parent Container DcmDspAddressAndLengthFormatIdentifier
Description This parameter defines the supported
AddressAndLengthFormatIdentifier of the request message.
Multiplicity 1..*
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Multiplicity

567 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Post-Build Variant false

Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers
DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspMemory:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspAddressAndLengthFormatIdentifier:
EcucParamConfContainerDef

lowerMultiplicity = 0
DcmDspSupportedAddressAndLengthFormatIdentifier:
upperMultiplicity = 1
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = *
min = 0
max = 255 A

Figure 10.35: DcmDspMemoryFormatIdentifier configuration overview

10.2.5.13.4 DcmDspMemoryIdInfo

SWS Item [ECUC_Dcm_00911]

Container Name DcmDspMemoryIdInfo
Parent Container DcmDspMemory
Description Provides the value of memory identifier used to select the desired
memory device

This container contains the configuration of the memory access

requested through diagnostic services : ReadMemoryByAddress,
WriteMemoryByAddress, and DynamicallyDefineDataIdentifier
Configuration Parameters

568 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspMemoryIdValue [ECUC_Dcm_00913]

Parent Container DcmDspMemoryIdInfo
Description Value of the memory device identifier used.

Each DcmDspMemoryIdInfo should have a unique ID.

The MemoryIdValue is retrieved from the request messages

(RMBA,WMBA,RD,RU,DDDI) according to ISO-14229-1 with the most
significant byte of the request parameter memoryAddress.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspReadMemory 0..* Provides a memory range allowed for reading via labels
RangeByLabelInfo (lower and higher address configured as strings).
DcmDspReadMemory 0..* Provides the range of memory address allowed for
RangeInfo reading
DcmDspWriteMemory 0..* Provides a memory range allowed for writing via labels
RangeByLabelInfo (lower and higher address configured as strings).
DcmDspWriteMemory 0..* Provides the range of memory address allowed for
RangeInfo writting.

569 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDsp:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspMemory:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspMemoryIdInfo:
EcucParamConfContainerDef DcmDspMemoryIdValue: EcucIntegerParamDef

lowerMultiplicity = 1 +parameter lowerMultiplicity = 0

upperMultiplicity = * upperMultiplicity = 1
min = 0
max = 255
A

DcmDspReadMemoryRangeInfo:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = *

DcmDspWriteMemoryRangeInfo:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = *

DcmDspReadMemoryRangeByLabelInfo:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = *

DcmDspWriteMemoryRangeByLabelInfo:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = *

Figure 10.36: DcmDspMemoryIdInfo configuration overview

10.2.5.13.5 DcmDspMemoryTransferIdInfo

SWS Item [ECUC_Dcm_01137]

Container Name DcmDspMemoryTransferIdInfo
Parent Container DcmDspMemoryTransfer
Description Provides the value of memory identifier used to select the desired
memory device

This container contains the configuration of the memory access

requested through diagnostic services : RequestDownload,
RequestUpload, TransferData, RequestTransferExit
Configuration Parameters

570 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspMemoryIdValue [ECUC_Dcm_01138]

Parent Container DcmDspMemoryTransferIdInfo
Description Value of the memory device identifier used.

Each DcmDspMemoryIdInfo should have a unique ID.

The MemoryIdValue is retrieved from the request messages

(RMBA,WMBA,RD,RU,DDDI) according to ISO-14229-1 with the most
significant byte of the request parameter memoryAddress.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.5.13.6 DcmDspReadMemoryRangeByLabelInfo

SWS Item [ECUC_Dcm_01068]

Container Name DcmDspReadMemoryRangeByLabelInfo
Parent Container DcmDspMemoryIdInfo
Description Provides a memory range allowed for reading via labels (lower and
higher address configured as strings).
Configuration Parameters

Name DcmDspReadMemoryRangeByLabelHigh [ECUC_Dcm_01070]

Parent Container DcmDspReadMemoryRangeByLabelInfo
Description High memory address as label (string) of a range allowed for reading.
Multiplicity 1
Type EcucStringParamDef
Default Value
Regular Expression [a-zA-Z0-9_]([a-zA-Z0-9\._])*
Post-Build Variant false
Value

571 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DcmDspReadMemoryRangeByLabelLow [ECUC_Dcm_01069]

Parent Container DcmDspReadMemoryRangeByLabelInfo
Description Low memory address as label (string) of a range allowed for reading.
Multiplicity 1
Type EcucStringParamDef
Default Value
Regular Expression [a-zA-Z0-9_]([a-zA-Z0-9\._])*
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DcmDspReadMemoryRangeModeRuleRef [ECUC_Dcm_01072]

Parent Container DcmDspReadMemoryRangeByLabelInfo
Description Reference to DcmModeRule

Mode rule which controls read access on this memory address. If there
is no reference, no check of the mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

572 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspReadMemoryRangeSecurityLevelRef [ECUC_Dcm_01071]

Parent Container DcmDspReadMemoryRangeByLabelInfo
Description Link to the Security Access Levels needed for read access on this
memory address. If there is no reference, no check of security level
shall be done.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspReadMemoryRangeSessionLevelRef [ECUC_Dcm_01088]

Parent Container DcmDspReadMemoryRangeByLabelInfo
Description Link to the session level needed for access to this memory address
range.

If there is no reference, no check of session level shall be done.

Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.5.13.7 DcmDspReadMemoryRangeInfo

SWS Item [ECUC_Dcm_00785]

573 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Container Name DcmDspReadMemoryRangeInfo

Parent Container DcmDspMemoryIdInfo
Description Provides the range of memory address allowed for reading
Configuration Parameters

Name DcmDspReadMemoryRangeHigh [ECUC_Dcm_00787]

Parent Container DcmDspReadMemoryRangeInfo
Description High memory address of a range allowed for reading
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 4294967294
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspReadMemoryRangeLow [ECUC_Dcm_00786]

Parent Container DcmDspReadMemoryRangeInfo
Description Low memory address of a range allowed for reading
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 4294967294
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspReadMemoryRangeModeRuleRef [ECUC_Dcm_00920]

Parent Container DcmDspReadMemoryRangeInfo
Description Reference to DcmModeRule

Mode rule which controls read access on this memory address. If there
is no reference, no check of the mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value

574 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,

Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspReadMemoryRangeSecurityLevelRef [ECUC_Dcm_00788]

Parent Container DcmDspReadMemoryRangeInfo
Description Link to the Security Access Levels needed for read access on this
memory address. If there is no reference, no check of security level
shall be done.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspReadMemoryRangeSessionLevelRef [ECUC_Dcm_01086]

Parent Container DcmDspReadMemoryRangeInfo
Description Link to the session level needed for access to this memory address
range.

If there is no reference, no check of session level shall be done.

Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –

575 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.5.13.8 DcmDspWriteMemoryRangeByLabelInfo

SWS Item [ECUC_Dcm_01073]

Container Name DcmDspWriteMemoryRangeByLabelInfo
Parent Container DcmDspMemoryIdInfo
Description Provides a memory range allowed for writing via labels (lower and
higher address configured as strings).
Configuration Parameters

Name DcmDspWriteMemoryRangeByLabelHigh [ECUC_Dcm_01075]

Parent Container DcmDspWriteMemoryRangeByLabelInfo
Description High memory address as label (string) of a range allowed for writing.
Multiplicity 1
Type EcucStringParamDef
Default Value
Regular Expression [a-zA-Z0-9_]([a-zA-Z0-9\._])*
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DcmDspWriteMemoryRangeByLabelLow [ECUC_Dcm_01074]

Parent Container DcmDspWriteMemoryRangeByLabelInfo
Description Low memory address as label (string) of a range allowed for writing.
Multiplicity 1
Type EcucStringParamDef
Default Value
Regular Expression [a-zA-Z0-9_]([a-zA-Z0-9\._])*
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –

576 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Scope / Dependency scope: local

Name DcmDspWriteMemoryRangeModeRuleRef [ECUC_Dcm_01077]

Parent Container DcmDspWriteMemoryRangeByLabelInfo
Description Reference to DcmModeRule

Mode rule which controls write access on this memory address. If

there is no reference, no check of the mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspWriteMemoryRangeSecurityLevelRef [ECUC_Dcm_01076]

Parent Container DcmDspWriteMemoryRangeByLabelInfo
Description Link to the Security Access Levels needed for write access on this
memory address. If there is no reference, no check of security level
shall be done.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

577 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspWriteMemoryRangeSessionLevelRef [ECUC_Dcm_01089]

Parent Container DcmDspWriteMemoryRangeByLabelInfo
Description Link to the session level needed for access to this memory address
range.

If there is no reference, no check of session level shall be done.

Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

578 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

No Included Containers
DcmDspReadMemoryRangeByLabelLow:
DcmDsp: DcmDspReadMemoryRangeByLabelInfo: EcucStringParamDef
EcucParamConfContainerDef EcucParamConfContainerDef
+parameter lowerMultiplicity = 1
lowerMultiplicity = 0 lowerMultiplicity = 0 upperMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = * regularExpression = [a-zA-Z0-9_]([a-zA-Z0-9\._])*
A

+subContainer DcmDspReadMemoryRangeByLabelHigh:
EcucStringParamDef
DcmDspMemory: +parameter
lowerMultiplicity = 1
EcucParamConfContainerDef
upperMultiplicity = 1
lowerMultiplicity = 0 regularExpression = [a-zA-Z0-9_]([a-zA-Z0-9\._])*
upperMultiplicity = 1 A

+subContainer DcmDspReadMemoryRangeSecurityLevelRef:
EcucReferenceDef
DcmDspMemoryIdInfo: +reference
EcucParamConfContainerDef lowerMultiplicity = 0
upperMultiplicity = *
lowerMultiplicity = 1
upperMultiplicity = * +subContainer

+reference DcmDspReadMemoryRangeModeRuleRef:
EcucReferenceDef

lowerMultiplicity = 0
upperMultiplicity = 1
+reference

DcmDspReadMemoryRangeSessionLevelRef:
EcucReferenceDef
DcmModeRule: +destination
lowerMultiplicity = 0
upperMultiplicity = * EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = *

+destination +destination
+destination
DcmDspSessionRow:
EcucParamConfContainerDef +destination DcmDspSecurityRow:
EcucParamConfContainerDef
upperMultiplicity = 31
lowerMultiplicity = 0 upperMultiplicity = 31
lowerMultiplicity = 0

+destination

DcmDspWriteMemoryRangeByLabelInfo: DcmDspWriteMemoryRangeSessionLevelRef:
EcucParamConfContainerDef EcucReferenceDef
+reference lowerMultiplicity = 0
lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = *

+subContainer
DcmDspWriteMemoryRangeModeRuleRef:
EcucReferenceDef
+reference
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspWriteMemoryRangeSecurityLevelRef:
EcucReferenceDef
+reference
lowerMultiplicity = 0
upperMultiplicity = *

+parameter
DcmDspWriteMemoryRangeByLabelHigh:
DcmDspWriteMemoryRangeByLabelLow: +parameter EcucStringParamDef
EcucStringParamDef
lowerMultiplicity = 1
lowerMultiplicity = 1 upperMultiplicity = 1
upperMultiplicity = 1 regularExpression = [a-zA-Z0-9_]([a-zA-Z0-9\._])*
regularExpression = [a-zA-Z0-9_]([a-zA-Z0-9\._])*
A
A

Figure 10.37: DcmDspMemoryReadWriteByLabel configuration overview

10.2.5.13.9 DcmDspWriteMemoryRangeInfo

579 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

SWS Item [ECUC_Dcm_00789]

Container Name DcmDspWriteMemoryRangeInfo
Parent Container DcmDspMemoryIdInfo
Description Provides the range of memory address allowed for writting.
Configuration Parameters

Name DcmDspWriteMemoryRangeHigh [ECUC_Dcm_00791]

Parent Container DcmDspWriteMemoryRangeInfo
Description High memory address of a range allowed for writing.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 4294967294
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspWriteMemoryRangeLow [ECUC_Dcm_00790]

Parent Container DcmDspWriteMemoryRangeInfo
Description Low memory address of a range allowed for writing
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 4294967294
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspWriteMemoryRangeModeRuleRef [ECUC_Dcm_00916]

Parent Container DcmDspWriteMemoryRangeInfo
Description Reference to DcmModeRule

Mode rule which controls write access on this memory address. If

there is no reference, no check of the mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value

580 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,

Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspWriteMemoryRangeSecurityLevelRef [ECUC_Dcm_00793]

Parent Container DcmDspWriteMemoryRangeInfo
Description Link to the Security Access Levels needed for write access on this
memory address. If there is no reference, no check of security level
shall be done.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspWriteMemoryRangeSessionLevelRef [ECUC_Dcm_01087]

Parent Container DcmDspWriteMemoryRangeInfo
Description Link to the session level needed for access to this memory address
range.

If there is no reference, no check of session level shall be done.

Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –

581 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

582 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

No Included Containers
DcmDspMemory:
EcucParamConfContainerDef DcmDsp: DcmDspReadMemoryRangeLow:
+subContainer EcucParamConfContainerDef EcucIntegerParamDef
lowerMultiplicity = 0
upperMultiplicity = 1 lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 +parameter upperMultiplicity = 1
min = 0
max = 4294967294 A

+subContainer

DcmDspMemoryIdInfo: DcmDspReadMemoryRangeHigh:
DcmDspReadMemoryRangeInfo: EcucIntegerParamDef
EcucParamConfContainerDef
EcucParamConfContainerDef
lowerMultiplicity = 1 lowerMultiplicity = 1
lowerMultiplicity = 0 +parameter upperMultiplicity = 1
upperMultiplicity = *
upperMultiplicity = * min = 0
max = 4294967294 A

+subContainer

DcmDspReadMemoryRangeSessionLevelRef:
+reference EcucReferenceDef

lowerMultiplicity = 0
upperMultiplicity = *

+reference
DcmDspReadMemoryRangeSecurityLevelRef:
EcucReferenceDef
+reference
lowerMultiplicity = 0
DcmDspReadMemoryRangeModeRuleRef: upperMultiplicity = *
EcucReferenceDef

lowerMultiplicity = 0
upperMultiplicity = 1

+destination
+destination

DcmDspSessionRow:
EcucParamConfContainerDef
DcmModeRule:
EcucParamConfContainerDef upperMultiplicity = 31
lowerMultiplicity = 0
lowerMultiplicity = 1 +destination
upperMultiplicity = *
+destination

+subContainer +destination
DcmDspWriteMemoryRangeInfo:
EcucParamConfContainerDef
DcmDspSecurityRow:
lowerMultiplicity = 0 EcucParamConfContainerDef
upperMultiplicity = * +destination
upperMultiplicity = 31
lowerMultiplicity = 0

DcmDspWriteMemoryRangeHigh:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
max = 4294967294 A DcmDspWriteMemoryRangeModeRuleRef:
+reference EcucReferenceDef

lowerMultiplicity = 0
DcmDspWriteMemoryRangeLow: upperMultiplicity = 1
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1 DcmDspWriteMemoryRangeSecurityLevelRef:
min = 0 EcucReferenceDef
max = 4294967294 A +reference
lowerMultiplicity = 0
upperMultiplicity = *

DcmDspWriteMemoryRangeSessionLevelRef:
EcucReferenceDef
+reference
lowerMultiplicity = 0
upperMultiplicity = *

Figure 10.38: DcmDspMemoryReadWrite configuration overview

583 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

10.2.5.14 PIDs

10.2.5.14.1 DcmDspPid

SWS Item [ECUC_Dcm_00626]

Container Name DcmDspPid
Parent Container DcmDsp
Description This container defines the availability of a PID to the DCM.
Configuration Parameters

Name DcmDspPidIdentifier [ECUC_Dcm_00627]

Parent Container DcmDspPid
Description 1 byte Identifier of the PID

Within each DcmConfigSet all DcmDspPidIdentifier values shall be

unique.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspPidService [ECUC_Dcm_00893]

Parent Container DcmDspPid
Description Indicates if a PID is used with service $01 and/or $02
Multiplicity 1
Type EcucEnumerationParamDef
Range DCM_SERVICE_01 A PID is used with service $01 only.
DCM_SERVICE_01_02 A PID is used with service $01 and
$02. Allowed with a PID configuration
containing data elements on byte
basis.
DCM_SERVICE_02 A PID is used with service $02 only.
Allowed with a PID configuration
containing data elements on byte
basis.
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

584 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspPidSize [ECUC_Dcm_00870]

Parent Container DcmDspPid
Description Length of a PID in byte(s).
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspPidUsed [ECUC_Dcm_00806]

Parent Container DcmDspPid
Description Allow to activate or deactivate the usage of a PID, for multi purpose
ECUs

true = PID is available false = PID is not available

Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant true
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspPidData 1..* This container defines the parameter for a Signal in the
PID.
DcmDspPidSupportInfo 0..* This container defines the support information (typically
byte A) to declare the usability of the data bytes within
the so-called packeted PIDs (e.g. PID$68).

585 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1
DcmDspPidUsed: EcucBooleanParamDef

upperMultiplicity = 1
+subContainer +parameter lowerMultiplicity = 1

DcmDspPid:
EcucParamConfContainerDef

upperMultiplicity = * DcmDspPidSize: EcucIntegerParamDef

lowerMultiplicity = 0 +parameter lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
max = 255 DcmDspPidIdentifier: EcucIntegerParamDef

lowerMultiplicity = 1
upperMultiplicity = 1
+parameter min = 0
max = 255

DcmDspPidSupportInfo: DcmDspPidSupportInfoPos:
EcucParamConfContainerDef EcucIntegerParamDef
+parameter
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = * upperMultiplicity = 1
min = 0
max = 255
+subContainer

DcmDspPidSupportInfoLen:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
max = 255
+destination

DcmDspPidDataSupportInfoRef:
EcucReferenceDef
+reference DcmDspPidDataSupportInfo:
lowerMultiplicity = 1 EcucParamConfContainerDef
upperMultiplicity = 1
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspPidDataSupportInfoBit:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
max = 255

DcmDspPidService: +literal DCM_SERVICE_01:

EcucEnumerationParamDef EcucEnumerationLiteralDef

+parameter +literal DCM_SERVICE_02:

EcucEnumerationLiteralDef

+literal DCM_SERVICE_01_02:
EcucEnumerationLiteralDef

Figure 10.39: DcmDspPid1 configuration overview

586 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspPid: DcmDspPidDataSupportInfo:
EcucParamConfContainerDef EcucParamConfContainerDef

upperMultiplicity = * lowerMultiplicity = 0
lowerMultiplicity = 0 upperMultiplicity = 1

+subContainer

+subContainer
DcmDspPidDataDemRef:
DcmDspPidData: DcmDspPidService02: EcucReferenceDef
EcucParamConfContainerDef +subContainer EcucParamConfContainerDef +reference
lowerMultiplicity = 0
lowerMultiplicity = 1 lowerMultiplicity = 0 upperMultiplicity = 1
upperMultiplicity = * upperMultiplicity = 1

+destination

DcmDspPidByteOffset: DemPidDataElement:
EcucIntegerParamDef EcucParamConfContainerDef
+parameter
min = 0 upperMultiplicity = 255
max = 255 lowerMultiplicity = 1
lowerMultiplicity = 1
upperMultiplicity = 1 (from Dem)

+parameter DcmDspPidDataByteSize:
EcucIntegerParamDef

min = 0
max = 255
lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspPidService01: DcmDspPidService01ExternalSRDataElementClass:
EcucParamConfContainerDef +subContainer EcucChoiceContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = 1

DcmDspDiagnosisScaling: EcucChoiceContainerDef

+subContainer lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspPidDataReadFnc: EcucFunctionNameDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspPidDataUsePort: +literal USE_DATA_SENDER_RECEIVER_AS_SERVICE:

EcucEnumerationParamDef EcucEnumerationLiteralDef

lowerMultiplicity = 1
upperMultiplicity = 1
+literal USE_DATA_SYNCH_CLIENT_SERVER:
EcucEnumerationLiteralDef

+parameter

+literal USE_DATA_SENDER_RECEIVER:
EcucEnumerationLiteralDef

+literal USE_DATA_SYNCH_FNC:
EcucEnumerationLiteralDef

Figure 10.40: DcmDspPid2 configuration overview

587 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspPidService01: DcmDspPidDataEndianness: +literal LITTLE_ENDIAN:

EcucParamConfContainerDef EcucEnumerationParamDef EcucEnumerationLiteralDef

lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 +parameter upperMultiplicity = 1
+literal OPAQUE: EcucEnumerationLiteralDef

+literal BIG_ENDIAN: EcucEnumerationLiteralDef

+parameter

DcmDspPidDataType: +literal BOOLEAN:

EcucEnumerationParamDef EcucEnumerationLiteralDef

lowerMultiplicity = 1 +literal UINT8:

upperMultiplicity = 1 EcucEnumerationLiteralDef

+literal SINT8:
EcucEnumerationLiteralDef

+literal UINT16:
EcucEnumerationLiteralDef

+literal SINT16:
EcucEnumerationLiteralDef

+literal UINT32:
EcucEnumerationLiteralDef

+literal SINT32:
EcucEnumerationLiteralDef

+literal UINT8_N:
EcucEnumerationLiteralDef

+literal SINT8_N:
EcucEnumerationLiteralDef

+literal UINT16_N:
EcucEnumerationLiteralDef

+literal SINT16_N:
EcucEnumerationLiteralDef

+literal UINT32_N:
EcucEnumerationLiteralDef

+literal SINT32_N:
EcucEnumerationLiteralDef

Figure 10.41: DcmDspPid3 configuration overview

10.2.5.14.2 DcmDspPidSupportInfo

SWS Item [ECUC_Dcm_00871]

Container Name DcmDspPidSupportInfo
Parent Container DcmDspPid
Description This container defines the support information (typically byte A) to
declare the usability of the data bytes within the so-called packeted
PIDs (e.g. PID$68).
Configuration Parameters

588 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspPidSupportInfoLen [ECUC_Dcm_00873]

Parent Container DcmDspPidSupportInfo
Description Length of the support information in bytes.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspPidSupportInfoPos [ECUC_Dcm_00872]

Parent Container DcmDspPidSupportInfo
Description Position of the support information in bytes.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.5.14.3 DcmDspPidData

SWS Item [ECUC_Dcm_00865]

Container Name DcmDspPidData
Parent Container DcmDspPid
Description This container defines the parameter for a Signal in the PID.
Configuration Parameters

589 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspPidByteOffset [ECUC_Dcm_01107]

Parent Container DcmDspPidData
Description This is the position in bytes of the PID structure and will not start at
position 0 in case a support information is available (for packeted
PIDs).
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspPidDataByteSize [ECUC_Dcm_01108]

Parent Container DcmDspPidData
Description Defines the array length in bytes or the the maximum array length for
variable datalengths.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspPidDataSupport 0..1 This container defines the supported information.
Info
DcmDspPidService01 0..1 Contains specific configuration parameter of PID for
service $01. This container exists only if
DcmDspPidService is set to DCM_SERVICE_01 or
DCM_SERVICE_01_02.
DcmDspPidService02 0..1 Contains specific configuration parameter of PID for
service $02. This container exists only if
DcmDspPidService is set to DCM_SERVICE_02 or
DCM_SERVICE_01_02.

590 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

10.2.5.14.4 DcmDspPidService01

SWS Item [ECUC_Dcm_00894]

Container Name DcmDspPidService01
Parent Container DcmDspPidData
Description Contains specific configuration parameter of PID for service $01. This
container exists only if DcmDspPidService is set to
DCM_SERVICE_01 or DCM_SERVICE_01_02.
Configuration Parameters

Name DcmDspPidDataEndianness [ECUC_Dcm_01012]

Parent Container DcmDspPidService01
Description Defines the endianness of the data belonging to a PID in a diagnostic
response message.

If no DcmDspPidDataEndianness is defined the value of

DcmDspDataDefaultEndianness is applicable.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at
the lowest address.
LITTLE_ENDIAN Most significant byte shall be stored at
the highest address
OPAQUE Opaque data endianness
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspPidDataReadFnc [ECUC_Dcm_00629]

Parent Container DcmDspPidService01
Description Function name for reading PID data value. This is only relevant if
DcmDspPidDataUsePort==USE_DATA_SYNCH_FNC.

This parameter is related to the interface Xxx_ReadData.

Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity

591 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Post-Build Variant false

Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspPidDataType [ECUC_Dcm_01018]

Parent Container DcmDspPidService01
Description Provide the implementation data type of data belonging to a PID.
Multiplicity 1
Type EcucEnumerationParamDef
Range BOOLEAN Type of the data is boolean.
SINT16 Type of the data is sint16.
SINT16_N Type of the data is sint16 array.
SINT32 Type of the data is sint32.
SINT32_N Type of the data is sint32 array.
SINT8 Type of the data is sint8.
SINT8_N Type of the data is sint8 array.
UINT16 Type of the data is uint16.
UINT16_N Type of the data is uint16 array.
UINT32 Type of the data is uint32.
UINT32_N Type of the data is uint32 array.
UINT8 Type of the data is uint8.
UINT8_N Type of the data is uint8 array.
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

592 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspPidDataUsePort [ECUC_Dcm_00720]

Parent Container DcmDspPidService01
Description If this parameter is set to USE_DATA_SYNCH_FNC, the Dcm will use
the function defined in DcmDspPidDataReadFnc to get the PID data
value.

If this parameter is set to USE_DATA_SYNCH_CLIENT_SERVER, the

Dcm will have an R-Port requiring the interface DataServices_{Data}.

If this parameter is set to USE_DATA_SENDER_RECEIVER or

USE_DATA_SENDER_RECEIVER_AS_SERVICE, the DCM will have
an R-Port requiring a SenderReceiverInterface.

The R-Port is named DataServices_{Data} where {Data} is the name of

the container DcmDspPidData.
Multiplicity 1
Type EcucEnumerationParamDef
Range USE_DATA_SENDER_RE
CEIVER
USE_DATA_SENDER_RE
CEIVER_AS_SERVICE
USE_DATA_SYNCH_CLI
ENT_SERVER
USE_DATA_SYNCH_FNC
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspDiagnosis 0..1 This container contains the configuration (parameters)
Scaling of an alternative Diagnosis Representation. Out if this
the scaling between Diagnosis and ECU internal
representation and vice versa can be calculated.
DcmDspPidService01 0..1 This container defines the source of data in a provided
ExternalSRDataElement port which shall be read respectively the target of data in
Class a required port which shall be written.

This container shall contain either one

DcmSubElementInDataElementInstance OR
DcmDataElementInstance OR
DcmSubElementInImplDataElementInstance reference.

10.2.5.14.5 DcmDspPidService02

SWS Item [ECUC_Dcm_00895]

Container Name DcmDspPidService02
Parent Container DcmDspPidData

593 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Description Contains specific configuration parameter of PID for service $02. This
container exists only if DcmDspPidService is set to
DCM_SERVICE_02 or DCM_SERVICE_01_02.
Configuration Parameters

Name DcmDspPidDataDemRef [ECUC_Dcm_00887]

Parent Container DcmDspPidService02
Description Reference to DemPidDataElement in DEM configuration. Allows to link
the DCM PID and DEM PID configuration for Mode $02.
Multiplicity 0..1
Type Reference to DemPidDataElement
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.5.14.6 DcmDspPidDataSupportInfo

SWS Item [ECUC_Dcm_00874]

Container Name DcmDspPidDataSupportInfo
Parent Container DcmDspPidData
Description This container defines the supported information.
Configuration Parameters

Name DcmDspPidDataSupportInfoBit [ECUC_Dcm_00876]

Parent Container DcmDspPidDataSupportInfo
Description Referenced Bit of the SupportInfo
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value

594 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspPidDataSupportInfoRef [ECUC_Dcm_00875]

Parent Container DcmDspPidDataSupportInfo
Description Reference to DcmDspPidSupportInfo
Multiplicity 1
Type Reference to DcmDspPidSupportInfo
false
Post-Build Variant
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.5.15 DcmDspRequestControl

SWS Item [ECUC_Dcm_00637]

Container Name DcmDspRequestControl
Parent Container DcmDsp
Description This container contains the configuration (parameters) of the "Request
control of on-board system, test or component" service (Service $08).
The DCM will request the control using an R-Port requiring a
PortInteface RequestControlServices_{Tid}. The R-Port is named
RequestControlServices_{Tid} where {Tid} is the name of the container
DcmDspRequestControl.
Configuration Parameters

Name DcmDspRequestControlInBufferSize [ECUC_Dcm_00722]

Parent Container DcmDspRequestControl
Description Number of bytes to be provided in the input buffer of the interface
RequestControlServices_{Tid} for OBD Service $08
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value

595 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRequestControlInfoByte [ECUC_Dcm_01078]

Parent Container DcmDspRequestControl
Description Manufacturer specific value reported to the tester for the record
identifiers 0xE000 to OxE1FF. (WWH-OBD use cases)
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRequestControlOutBufferSize [ECUC_Dcm_00723]

Parent Container DcmDspRequestControl
Description Number of bytes to be provided in the output buffer of the interface
RequestControlServices_{Tid} for OBD Service $08
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRequestControlTestId [ECUC_Dcm_00656]

Parent Container DcmDspRequestControl
Description Test Id for Service $08
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value

596 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

No Included Containers
DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspRequestControl: DcmDspRequestControlTestId:
EcucParamConfContainerDef EcucIntegerParamDef

upperMultiplicity = * +parameter lowerMultiplicity = 1

lowerMultiplicity = 0 upperMultiplicity = 1
min = 0
max = 255

DcmDspRequestControlInBufferSize:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
max = 255

DcmDspRequestControlOutBufferSize:
EcucIntegerParamDef
+parameter
upperMultiplicity = 1
lowerMultiplicity = 1
min = 0
max = 255

DcmDspRequestControlInfoByte:
EcucIntegerParamDef
+parameter lowerMultiplicity = 0
upperMultiplicity = 1
min = 0
max = 255

Figure 10.42: DcmDspRequestControl configuration overview

10.2.5.16 DcmDspRequestFileTransfer

SWS Item [ECUC_Dcm_01034]

Container Name DcmDspRequestFileTransfer
Parent Container DcmDsp
Description This container contains the configuration for RequestFileTransfer. This
container only exists if RequestFileTransfer is configured.
Configuration Parameters

597 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmRequestFileTransferFileSizeOrDirInfoParameterLength
[ECUC_Dcm_01035]
Parent Container DcmDspRequestFileTransfer
Description Defines the length (number of bytes, i.e. the value of
fileSizeOrDirInfoParameterLength) of the
fileSizeUncompressedOrDirInfoLength and fileSizeCompressed in the
response of RequestFileTransfer.
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 4
Default Value 4
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmRequestFileTransferLengthFormatIdentifier [ECUC_Dcm_01036]

Parent Container DcmDspRequestFileTransfer
Description Defines the length (number of bytes) of the maxNumberOfBlockLength
parameter in the response of RequestFileTransfer.
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 4
Default Value 4
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmRequestFileTransferMaxFileAndDirName [ECUC_Dcm_01130]

Parent Container DcmDspRequestFileTransfer
Description Defines the maximum size allowed for the FileAndDirName parameter
with RTE interfaces used for RequestFileTransfer.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 65535
Default Value 1
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

598 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmRequestFileTransferUsePort [ECUC_Dcm_01131]

Parent Container DcmDspRequestFileTransfer
Description Defines if a C/S or C function call shall be used for RequestFileTransfer
processing.
Multiplicity 1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

No Included Containers
DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspRequestFileTransfer: DcmRequestFileTransferFileSizeOrDirInfoParameterLength:
EcucParamConfContainerDef EcucIntegerParamDef
+parameter min = 1
lowerMultiplicity = 0
upperMultiplicity = 1 max = 4
defaultValue = 4
lowerMultiplicity = 1
upperMultiplicity = 1

DcmRequestFileTransferLengthFormatIdentifier:
EcucIntegerParamDef
+parameter min = 1
max = 4
defaultValue = 4
lowerMultiplicity = 1
upperMultiplicity = 1

DcmRequestFileTransferMaxFileAndDirName:
EcucIntegerParamDef
+parameter min = 1
max = 65535
defaultValue = 1
lowerMultiplicity = 0
upperMultiplicity = 1

DcmRequestFileTransferUsePort:
+parameter EcucBooleanParamDef

defaultValue = false
lowerMultiplicity = 1
upperMultiplicity = 1

Figure 10.43: DcmDspRequestFileTransfer configuration overview

10.2.5.17 Response on Event

10.2.5.17.1 DcmDspRoe

SWS Item [ECUC_Dcm_00858]

Container Name DcmDspRoe

599 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Parent Container DcmDsp

Description Provide the configuration of the ResponseOnEvent mechanism.
Configuration Parameters

Name DcmDspRoeInterMessageTime [ECUC_Dcm_00856]

Parent Container DcmDspRoe
Description Provide the minimum time in seconds between two transmissions of
ROE event. It is used for the delay between two different consecutive
Roe transmissions.
Multiplicity 1
Type EcucFloatParamDef
Range [0 .. 5]
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspRoeEvent 1..255 This container contains a list of all supported Roe
eventTypeRecords which are accepted by this ECU.

At most one DcmDspRoeEvent container is allowed to

define a DcmDspRoeEventProperties container with the
choice DcmDspRoeOnDTCStatusChange.
DcmDspRoeEvent 1..* This container configures the available
WindowTime EventWindowTime in this Ecu.

This container contains a sub-set of EventWindowTimes

supported by the Dcm, to limit the Ecu resources.

600 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1
+literal
DcmDspRoeEventWindowTime: DCM_ROE_EVENT_WINDOW_INFINITE:
EcucEnumerationParamDef EcucEnumerationLiteralDef

upperMultiplicity = 1
+subContainer lowerMultiplicity = 1

DcmDspRoe: +parameter +literal

EcucParamConfContainerDef
DCM_ROE_EVENT_WINDOW_CURRENT_CYCLE:
lowerMultiplicity = 0 EcucEnumerationLiteralDef
upperMultiplicity = 1
+literal

DCM_ROE_EVENT_WINDOW_CURRENT_AND_FOLLOWING_CYCLE:
EcucEnumerationLiteralDef

DcmDspRoeEventWindowTime:
+subContainer EcucParamConfContainerDef
DcmDspRoeInterMessageTime:
lowerMultiplicity = 1
EcucFloatParamDef
upperMultiplicity = *
min = 0
lowerMultiplicity = 1
+parameter upperMultiplicity = 1
max = 5

DcmDspRoeEvent:
EcucParamConfContainerDef
+subContainer DCM_ROE_CLEARED:
lowerMultiplicity = 1 EcucEnumerationLiteralDef
upperMultiplicity = 255
+literal

+parameter DcmDspRoeInitialEventStatus:
+parameter EcucEnumerationParamDef

DcmDspRoeEventId: upperMultiplicity = 1
EcucIntegerParamDef lowerMultiplicity = 1
+subContainer
defaultValue = DCM_ROE_CLEARED
lowerMultiplicity = 1
DcmDspRoeEventProperties:
upperMultiplicity = 1
EcucChoiceContainerDef
min = 0
lowerMultiplicity = 1 max = 254
upperMultiplicity = 1 symbolicNameValue = true A

+literal

DCM_ROE_STOPPED:
EcucEnumerationLiteralDef

+choice +subContainer

DcmDspRoeOnChangeOfDataIdentifier: DcmDspRoeDidRef: DcmDspDid:

EcucParamConfContainerDef EcucReferenceDef EcucParamConfContainerDef
+reference +destination
lowerMultiplicity = 0 lowerMultiplicity = 1 upperMultiplicity = *
upperMultiplicity = 1 upperMultiplicity = 1 lowerMultiplicity = 0

+choice

DcmDspRoeDTCStatusMask:
DcmDspRoeOnDTCStatusChange:
EcucIntegerParamDef
EcucParamConfContainerDef
+parameter min = 0
lowerMultiplicity = 0
max = 255
upperMultiplicity = 1
lowerMultiplicity = 0
upperMultiplicity = 1
A

Figure 10.44: DcmDspRoe configuration overview

10.2.5.17.2 DcmDspRoeEvent

SWS Item [ECUC_Dcm_00973]

Container Name DcmDspRoeEvent
Parent Container DcmDspRoe

601 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Description This container contains a list of all supported Roe eventTypeRecords

which are accepted by this ECU.

At most one DcmDspRoeEvent container is allowed to define a

DcmDspRoeEventProperties container with the choice
DcmDspRoeOnDTCStatusChange.
Configuration Parameters

Name DcmDspRoeEventId [ECUC_Dcm_00976]

Parent Container DcmDspRoeEvent
Description EventId for a global identification of this ROE event it is used within
APIs Dcm_TriggerOnEvent() and the ModeDeclarationGroup.

The ratio Ids should be sequentially ordered beginning with 0 and no

gaps in between.
Multiplicity 1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 0 .. 254
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DcmDspRoeInitialEventStatus [ECUC_Dcm_00980]

Parent Container DcmDspRoeEvent
Description Initial Roe status of this RoeEvent
Multiplicity 1
Type EcucEnumerationParamDef
Range DCM_ROE_CLEARED
DCM_ROE_STOPPED
Default Value DCM_ROE_CLEARED
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

602 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspRoeEvent 1 This container contains the properties of Roe
Properties eventTypeRecords.

In one DcmDspRoeEventProperties container one

DcmDspRoeOnDTCStatusChange or
DcmDspRoeOnChangeOfDataIdentifier container shall
be defined.

10.2.5.17.3 DcmDspRoeEventProperties

SWS Item [ECUC_Dcm_00978]

Container Name DcmDspRoeEventProperties
Parent Container DcmDspRoeEvent
Description This container contains the properties of Roe eventTypeRecords.

In one DcmDspRoeEventProperties container one

DcmDspRoeOnDTCStatusChange or
DcmDspRoeOnChangeOfDataIdentifier container shall be defined.
Configuration Parameters

Container Choices
Container Name Multiplicity Scope / Dependency
DcmDspRoeOnChange 0..1 This container contains the eventTypeRecord supported
OfDataIdentifier for onChangeOfDataIdentifier eventType.
DcmDspRoeOnDTC 0..1 This container contains the eventTypeRecord supported
StatusChange for onDTCStatusChange eventType.

10.2.5.17.4 DcmDspRoeOnChangeOfDataIdentifier

SWS Item [ECUC_Dcm_00975]

Container Name DcmDspRoeOnChangeOfDataIdentifier
Parent Container DcmDspRoeEventProperties
Description This container contains the eventTypeRecord supported for
onChangeOfDataIdentifier eventType.
Configuration Parameters

Name DcmDspRoeDidRef [ECUC_Dcm_00979]

Parent Container DcmDspRoeOnChangeOfDataIdentifier
Description Reference to a Did which is watched.
Multiplicity 1
Type Reference to DcmDspDid
false
Post-Build Variant
Value

603 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

No Included Containers

10.2.5.17.5 DcmDspRoeOnDTCStatusChange

SWS Item [ECUC_Dcm_00974]

Container Name DcmDspRoeOnDTCStatusChange
Parent Container DcmDspRoeEventProperties
Description This container contains the eventTypeRecord supported for
onDTCStatusChange eventType.
Configuration Parameters

Name DcmDspRoeDTCStatusMask [ECUC_Dcm_01109]

Parent Container DcmDspRoeOnDTCStatusChange
Description Value of the relevant DTCStatusMask
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

No Included Containers

10.2.5.17.6 DcmDspRoeEventWindowTime

SWS Item [ECUC_Dcm_00981]

Container Name DcmDspRoeEventWindowTime
Parent Container DcmDspRoe
Description This container configures the available EventWindowTime in this Ecu.

This container contains a sub-set of EventWindowTimes supported by

the Dcm, to limit the Ecu resources.

604 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Configuration Parameters

Name DcmDspRoeEventWindowTime [ECUC_Dcm_00982]

Parent Container DcmDspRoeEventWindowTime
Description Value of the EventWindowTime
Multiplicity 1
Type EcucEnumerationParamDef
Range DCM_ROE_EVENT_WIN
DOW_CURRENT_AND_F
OLLOWING_CYCLE
DCM_ROE_EVENT_WIN
DOW_CURRENT_CYCLE
DCM_ROE_EVENT_WIN
DOW_INFINITE
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

No Included Containers

605 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

10.2.5.18 Routines

DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspRoutine: DcmDspRoutineIdentifier: EcucIntegerParamDef

EcucParamConfContainerDef +parameter
lowerMultiplicity = 1
upperMultiplicity = * upperMultiplicity = 1
lowerMultiplicity = 0 min = 0
max = 65535

+parameter DcmDspRoutineUsePort: EcucBooleanParamDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspRoutineUsed: EcucBooleanParamDef
+parameter
upperMultiplicity = 1
lowerMultiplicity = 1

DcmDspStartRoutine: EcucParamConfContainerDef
+subContainer
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspStopRoutine: EcucParamConfContainerDef
+subContainer
upperMultiplicity = 1
lowerMultiplicity = 0

DcmDspRequestRoutineResults:
+subContainer EcucParamConfContainerDef

upperMultiplicity = 1
lowerMultiplicity = 0

DcmDspRequestControl:
EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

DcmDspRoutineInfoByte: EcucIntegerParamDef

+parameter lowerMultiplicity = 0
upperMultiplicity = 1
min = 0
max = 255

Figure 10.45: DcmDspRoutine configuration overview

10.2.5.18.1 DcmDspRoutine

SWS Item [ECUC_Dcm_00640]

Container Name DcmDspRoutine
Parent Container DcmDsp
Description This container contains the configuration (parameters) for Routines
Configuration Parameters

606 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspRoutineIdentifier [ECUC_Dcm_00641]

Parent Container DcmDspRoutine
Description 2 bytes Identifier of the RID

Within each DcmConfigSet all DcmDspRoutineIdentifier values shall be

unique.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineInfoByte [ECUC_Dcm_01063]

Parent Container DcmDspRoutine
Description Manufacturer specific value reported to the tester for the record
identifiers 0xE000 to OxE1FF. (OBD use cases)
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineUsed [ECUC_Dcm_00807]

Parent Container DcmDspRoutine
Description Allow to activate or deactivate the usage of a Routine, for multi purpose
ECUs

True = Routine is available False = Routine is not available

Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant true
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

607 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspRoutineUsePort [ECUC_Dcm_00724]

Parent Container DcmDspRoutine
Description If this parameter is set to true, the DCM uses a port requiring a
PortInterface RoutineServices_{RoutineName}.

The R-Port is named RoutineServices_{RoutineName} where

{RoutineName} is the name of the container DcmDspRoutine In that
case, the configuration must not provide function names in
DcmDspStartRoutineFnc, DcmDspStopRoutineFnc or
DcmDspRequestResultsRoutineFnc. If this is false, the DCM expects
to find the names of the functions to be used in
DcmDspStartRoutineFnc, DcmDspStopRoutineFnc or
DcmDspRequestResultsRoutineFnc.
Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspRequestRoutine 0..1 Provides the configuration of RequestResult subservice
Results for RoutineControl service. Existence indicates that the
RequestRoutineResults in the RoutineControl is
supported.
DcmDspStartRoutine 0..1 Provides the configuration of Start subservice for
RoutineControl service.
DcmDspStopRoutine 0..1 Provides the configuration of Stop subservice for
RoutineControl service. Existence indicates that the
StopRoutine in the RoutineControl is supported.

10.2.5.18.2 DcmDspRequestRoutineResults

SWS Item [ECUC_Dcm_01023]

Container Name DcmDspRequestRoutineResults
Parent Container DcmDspRoutine
Description Provides the configuration of RequestResult subservice for
RoutineControl service. Existence indicates that the
RequestRoutineResults in the RoutineControl is supported.
Configuration Parameters

608 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspRequestRoutineResultsConfirmationEnabled
[ECUC_Dcm_01091]
Parent Container DcmDspRequestRoutineResults
Description Allows to enable/disable the confirmation function to indicate the
transmission of a response to a RequestRoutineResults request
Multiplicity 0..1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRequestRoutineResultsConfirmationFnc [ECUC_Dcm_01090]

Parent Container DcmDspRequestRoutineResults
Description C-function to call if a transmission confirmation is needed by the issuer
(BSW module)
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

609 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspRequestRoutineResultsFnc [ECUC_Dcm_00753]

Parent Container DcmDspRequestRoutineResults
Description Function name for request to application the results of a routine.
(Routine_RequestResults-function)

This parameter is related to the interface Xxx_RequestResults.

Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRequestRoutineResultsRole [ECUC_Dcm_01146]

Parent Container DcmDspRequestRoutineResults
Description Bitfield were each bit represents one dedicated role. A RoutineControl
with sub-function requestResults is granted access if the bit value is 1.
If a bit value is 0, the routine is not allowed for that role.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 4294967295
Default Value
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

610 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspRoutineInterfaceArgumentIntegrity [ECUC_Dcm_01184]

Parent Container DcmDspRequestRoutineResults
Description Defines the value of ClientServerOperation.diagArgIntegrity for the
created C/S interface of this routine
Multiplicity 0..1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRequestRoutineResultsCommonAuthorizationRef
[ECUC_Dcm_01054]
Parent Container DcmDspRequestRoutineResults
Description Reference to DcmDspCommonAuthorization

Common authorization configuration taken from the referenced

DcmDspRequestRoutineResultsCommonAuthorizationRef. If there is
no reference, no check on the commonly defined authorization
conditions shall be done to get the routine result.
Multiplicity 0..1
Type Reference to DcmDspCommonAuthorization
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspRequestRoutine 0..1 Provide description of input parameter of RequestResult
ResultsIn subservice for RoutineControl service.

611 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspRequestRoutine 0..1 Provide description of output parameter of

ResultsOut RequestResult subservice for RoutineControl service.

DcmDspRoutine:
EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

+subContainer
DcmDspRequestRoutineResultsOutSignal:
DcmDspRequestRoutineResults: DcmDspRequestRoutineResultsOut:
EcucParamConfContainerDef
EcucParamConfContainerDef +subContainer EcucParamConfContainerDef +subContainer
upperMultiplicity = *
upperMultiplicity = 1 upperMultiplicity = 1
lowerMultiplicity = 1
lowerMultiplicity = 0 lowerMultiplicity = 0
requiresIndex = true

DcmDspRequestRoutineResultsIn: DcmDspRequestRoutineResultsInSignal:
+subContainer EcucParamConfContainerDef +subContainer EcucParamConfContainerDef

upperMultiplicity = 1 upperMultiplicity = *
lowerMultiplicity = 0 lowerMultiplicity = 1
requiresIndex = true

DcmDspRequestRoutineResultsCommonAuthorizationRef: DcmDspCommonAuthorization:
+reference EcucReferenceDef +destination EcucParamConfContainerDef
lowerMultiplicity = 0 upperMultiplicity = *
upperMultiplicity = 1 lowerMultiplicity = 0

+parameter DcmDspRequestRoutineResultsFnc: EcucFunctionNameDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspRequestRoutineResultsRole:
EcucIntegerParamDef
+parameter
min = 0
max = 4294967295
DcmDspRequestRoutineResultsConfirmationEnabled:
lowerMultiplicity = 0
EcucBooleanParamDef
+parameter upperMultiplicity = 1
lowerMultiplicity = 0
upperMultiplicity = 1
defaultValue = FALSE

DcmDspRequestRoutineResultsConfirmationFnc:
+parameter EcucFunctionNameDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspRoutineInterfaceArgumentIntegrity:
EcucBooleanParamDef
+parameter
defaultValue = false
lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.46: DcmDspRequestRoutineResults configuration overview

10.2.5.18.3 DcmDspRequestRoutineResultsIn

SWS Item [ECUC_Dcm_01116]

Container Name DcmDspRequestRoutineResultsIn
Parent Container DcmDspRequestRoutineResults
Description Provide description of input parameter of RequestResult subservice for
RoutineControl service.

612 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Configuration Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspRequestRoutine 1..* Provides description of a routine signal used in
ResultsInSignal RoutineControl service.

The ordering defined via the index attribute of the

subcontainers in this list represents the order of the
dataIn_n elements in the XXX_RequestResult function
call.

10.2.5.18.4 DcmDspRequestRoutineResultsInSignal

SWS Item [ECUC_Dcm_01117]

Container Name DcmDspRequestRoutineResultsInSignal
Parent Container DcmDspRequestRoutineResultsIn
Description Provides description of a routine signal used in RoutineControl service.

The ordering defined via the index attribute of the subcontainers in this
list represents the order of the dataIn_n elements in the
XXX_RequestResult function call.

Attributes:
requiresIndex=true
Configuration Parameters

Name DcmDspRoutineParameterSize [ECUC_Dcm_01119]

Parent Container DcmDspRequestRoutineResultsInSignal
Description Provide the size of a RoutineControl parameter in bytes
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

613 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspRoutineSignalEndianness [ECUC_Dcm_01121]

Parent Container DcmDspRequestRoutineResultsInSignal
Description Defines the endianness of the data belonging to a Routine In Signal for
RequestResult subfunction.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at
the lowest address.
LITTLE_ENDIAN Most significant byte shall be stored at
the highest address
OPAQUE Opaque data endianness
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalPos [ECUC_Dcm_01118]

Parent Container DcmDspRequestRoutineResultsInSignal
Description Provide the position of the signal in the RoutineControl
request/response. The position is defined in bits.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalType [ECUC_Dcm_01120]

Parent Container DcmDspRequestRoutineResultsInSignal
Description Provide the type of the signal in the RoutineControl request/response.
Multiplicity 1
Type EcucEnumerationParamDef
Range BOOLEAN Type of the signal is boolean.
FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 Type of the signal is sint16.

614 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

SINT16_N Type of the signal is sint16 array.

SINT32 Type of the signal is sint32.
SINT32_N Type of the signal is sint32 array.
SINT8 Type of the signal is sint8.
SINT8_N Type of the signal is sint8 array.
UINT16 Type of the signal is uint16.
UINT16_N Type of the signal is uint16 array.
UINT32 Type of the signal is uint32.
UINT32_N Type of the signal is uint32 array.
UINT8 Type of the signal is uint8.
UINT8_N Type of the signal is uint8 array.
VARIABLE_LENGTH Type of the signal is
uint8[DcmDspRoutineParameterSize].

This is only valid for the last signal and

when DcmDspRoutineSignalType is
set to VARIABLE_LENGTH.
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspArgument 0..1 This container contains the configuration (arguments) of
Scaling an alternative Diagnosis Representation. Out if this the
scaling between Diagnosis and ECU internal
representation and vice versa can be calculated.

10.2.5.18.5 DcmDspRequestRoutineResultsOut

SWS Item [ECUC_Dcm_00831]

Container Name DcmDspRequestRoutineResultsOut
Parent Container DcmDspRequestRoutineResults
Description Provide description of output parameter of RequestResult subservice
for RoutineControl service.
Configuration Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspRequestRoutine 1..* Provides description of a routine signal used in
ResultsOutSignal RoutineControl service.

The ordering defined via the index attribute of the

subcontainers in this list represents the order of the
dataOutN elements in the XXX_RequestResult function
call.

615 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

10.2.5.18.6 DcmDspRequestRoutineResultsOutSignal

SWS Item [ECUC_Dcm_00836]

Container Name DcmDspRequestRoutineResultsOutSignal
Parent Container DcmDspRequestRoutineResultsOut
Description Provides description of a routine signal used in RoutineControl service.

The ordering defined via the index attribute of the subcontainers in this
list represents the order of the dataOutN elements in the
XXX_RequestResult function call.

Attributes:
requiresIndex=true
Configuration Parameters

Name DcmDspRoutineParameterSize [ECUC_Dcm_00838]

Parent Container DcmDspRequestRoutineResultsOutSignal
Description Provide the size of a RoutineControl parameter in bytes
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalEndianness [ECUC_Dcm_01013]

Parent Container DcmDspRequestRoutineResultsOutSignal
Description Defines the endianness of the data belonging to a Routine Out Signal
for RequestResult subfunction.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at
the lowest address.
LITTLE_ENDIAN Most significant byte shall be stored at
the highest address
OPAQUE Opaque data endianness
Post-Build Variant false
Multiplicity

616 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Post-Build Variant false

Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalPos [ECUC_Dcm_00837]

Parent Container DcmDspRequestRoutineResultsOutSignal
Description Provide the position of the signal in the RoutineControl
request/response. The position is defined in bits.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalType [ECUC_Dcm_00881]

Parent Container DcmDspRequestRoutineResultsOutSignal
Description Provide the type of the signal in the RoutineControl request/response.
Multiplicity 1
Type EcucEnumerationParamDef
Range BOOLEAN Type of the signal is boolean.
FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 Type of the signal is sint16.
SINT16_N Type of the signal is sint16 array.
SINT32 Type of the signal is sint32.
SINT32_N Type of the signal is sint32 array.
SINT8 Type of the signal is sint8.
SINT8_N Type of the signal is sint8 array.
UINT16 Type of the signal is uint16.
UINT16_N Type of the signal is uint16 array.
UINT32 Type of the signal is uint32.
UINT32_N Type of the signal is uint32 array.
UINT8 Type of the signal is uint8.
UINT8_N Type of the signal is uint8 array.

617 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

VARIABLE_LENGTH Type of the signal is

uint8[DcmDspRoutineParameterSize].

This is only valid for the last signal and

when DcmDspRoutineSignalType is
set to VARIABLE_LENGTH.
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspArgument 0..1 This container contains the configuration (arguments) of
Scaling an alternative Diagnosis Representation. Out if this the
scaling between Diagnosis and ECU internal
representation and vice versa can be calculated.

10.2.5.18.7 DcmDspStartRoutine

SWS Item [ECUC_Dcm_01021]

Container Name DcmDspStartRoutine
Parent Container DcmDspRoutine
Description Provides the configuration of Start subservice for RoutineControl
service.
Configuration Parameters

Name DcmDspRoutineInterfaceArgumentIntegrity [ECUC_Dcm_01184]

Parent Container DcmDspStartRoutine
Description Defines the value of ClientServerOperation.diagArgIntegrity for the
created C/S interface of this routine
Multiplicity 0..1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –

618 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Scope / Dependency scope: ECU

Name DcmDspStartRoutineConfirmationEnabled [ECUC_Dcm_01093]

Parent Container DcmDspStartRoutine
Description Allows to enable/disable the confirmation function to indicate the
transmission of a response to a StartRoutine request
Multiplicity 0..1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspStartRoutineConfirmationFnc [ECUC_Dcm_01094]

Parent Container DcmDspStartRoutine
Description C-function to call if a transmission confirmation is needed by the issuer
(BSW module)
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

619 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspStartRoutineFnc [ECUC_Dcm_00664]

Parent Container DcmDspStartRoutine
Description Function name for request to application to start a routine.
(Routine_Start-function)

This parameter is related to the interface Xxx_Start.

Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspStartRoutineRole [ECUC_Dcm_01144]

Parent Container DcmDspStartRoutine
Description Bitfield were each bit represents one dedicated role. A RoutineControl
with sub-function startRoutine is granted access if the bit value is 1. If a
bit value is 0, the routine is not allowed for that role.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 4294967295
Default Value
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

620 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspStartRoutineCommonAuthorizationRef [ECUC_Dcm_01052]

Parent Container DcmDspStartRoutine
Description Reference to DcmDspCommonAuthorization

Common authorization configuration taken from the referenced

DcmDspStartRoutineCommonAuthorizationRef. If there is no
reference, no check on the commonly defined authorization conditions
shall be done to start the routine.
Multiplicity 0..1
Type Reference to DcmDspCommonAuthorization
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStartRoutineIn 0..1 Provide description of input parameter of Start
subservice for RoutineControl service
DcmDspStartRoutineOut 0..1 Provide description of output parameter of Start
subservice for RoutineControl service.

621 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspRoutine:
EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

+subContainer
DcmDspStartRoutineInSignal:
DcmDspStartRoutine: DcmDspStartRoutineIn:
EcucParamConfContainerDef
EcucParamConfContainerDef +subContainer EcucParamConfContainerDef
+subContainer
upperMultiplicity = *
lowerMultiplicity = 0 upperMultiplicity = 1
lowerMultiplicity = 1
upperMultiplicity = 1 lowerMultiplicity = 0
requiresIndex = true

DcmDspStartRoutineOutSignal:
DcmDspStartRoutineOut:
EcucParamConfContainerDef
+subContainer EcucParamConfContainerDef +subContainer
upperMultiplicity = *
upperMultiplicity = 1
lowerMultiplicity = 1
lowerMultiplicity = 0
requiresIndex = true

DcmDspStartRoutineCommonAuthorizationRef: DcmDspCommonAuthorization:
+reference EcucReferenceDef +destination EcucParamConfContainerDef

lowerMultiplicity = 0 upperMultiplicity = *
upperMultiplicity = 1 lowerMultiplicity = 0

DcmDspStartRoutineFnc: EcucFunctionNameDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1 DcmDspStartRoutineRole:
EcucIntegerParamDef
+parameter
min = 0
max = 4294967295
lowerMultiplicity = 0
DcmDspStartRoutineConfirmationEnabled:
upperMultiplicity = 1
EcucBooleanParamDef
+parameter
defaultValue = false
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspStartRoutineConfirmationFnc:
+parameter EcucFunctionNameDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspRoutineInterfaceArgumentIntegrity:
EcucBooleanParamDef
+parameter
defaultValue = false
lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.47: DcmDspStartRoutine configuration overview

10.2.5.18.8 DcmDspStartRoutineIn

SWS Item [ECUC_Dcm_00834]

Container Name DcmDspStartRoutineIn
Parent Container DcmDspStartRoutine
Description Provide description of input parameter of Start subservice for
RoutineControl service
Configuration Parameters

622 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStartRoutineIn 1..* Provide description of a routine signal used in
Signal RoutineControl service.

The ordering defined via the index attribute of the

subcontainers in this list represents the order of the
dataInN elements in the XXX_Start function call.

623 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspRoutineSignalPos: DcmDspStartRoutineIn: DcmDspRoutineParameterSize:

EcucIntegerParamDef EcucParamConfContainerDef EcucIntegerParamDef

lowerMultiplicity = 1 upperMultiplicity = 1 lowerMultiplicity = 0

upperMultiplicity = 1 lowerMultiplicity = 0 upperMultiplicity = 1
min = 0 min = 0
max = 65535 max = 65535 A UINT8:
A
EcucEnumerationLiteralDef
+parameter +literal
+parameter

+subContainer
UINT8_N:
BOOLEAN: +literal EcucEnumerationLiteralDef
DcmDspStartRoutineInSignal: EcucEnumerationLiteralDef
EcucParamConfContainerDef

upperMultiplicity = * SINT8_N:
+literal
lowerMultiplicity = 1 EcucEnumerationLiteralDef
requiresIndex = true +literal
DcmDspRoutineSignalType:
EcucEnumerationParamDef
SINT8:
lowerMultiplicity = 1
+literal EcucEnumerationLiteralDef
upperMultiplicity = 1

+literal UINT16:
EcucEnumerationLiteralDef

+literal UINT16_N:
EcucEnumerationLiteralDef

+literal SINT16_N:
EcucEnumerationLiteralDef
+parameter

+literal SINT16:
EcucEnumerationLiteralDef

+literal UINT32:
EcucEnumerationLiteralDef

+literal SINT32:
EcucEnumerationLiteralDef

+literal UINT32_N:
EcucEnumerationLiteralDef

+literal
SINT32_N:
EcucEnumerationLiteralDef
+literal

FLOAT:
EcucEnumerationLiteralDef

+literal +literal

FLOAT_N: VARIABLE_LENGTH:
EcucEnumerationLiteralDef EcucEnumerationLiteralDef

LITTLE_ENDIAN:
+literal EcucEnumerationLiteralDef
DcmDspRoutineSignalEndianness:
+parameter EcucEnumerationParamDef
+literal OPAQUE:
lowerMultiplicity = 0 EcucEnumerationLiteralDef
upperMultiplicity = 1
+literal

BIG_ENDIAN:
DcmDspArgumentScaling: EcucEnumerationLiteralDef
+subContainer EcucChoiceContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.48: DcmDspStartRoutineIn configuration overview

10.2.5.18.9 DcmDspStartRoutineInSignal

SWS Item [ECUC_Dcm_00845]

624 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Container Name DcmDspStartRoutineInSignal

Parent Container DcmDspStartRoutineIn
Description Provide description of a routine signal used in RoutineControl service.

The ordering defined via the index attribute of the subcontainers in this
list represents the order of the dataInN elements in the XXX_Start
function call.

Attributes:
requiresIndex=true
Configuration Parameters

Name DcmDspRoutineParameterSize [ECUC_Dcm_00847]

Parent Container DcmDspStartRoutineInSignal
Description Provide the size of a RoutineControl parameter in bytes
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalEndianness [ECUC_Dcm_01016]

Parent Container DcmDspStartRoutineInSignal
Description Defines the endianness of the data belonging to a Routine In Signal for
Start subfunction.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at
the lowest address.
LITTLE_ENDIAN Most significant byte shall be stored at
the highest address
OPAQUE Opaque data endianness
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value

625 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,

Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalPos [ECUC_Dcm_00846]

Parent Container DcmDspStartRoutineInSignal
Description Provide the position of the signal in the RoutineControl
request/response. The position is defined in bits.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalType [ECUC_Dcm_00884]

Parent Container DcmDspStartRoutineInSignal
Description Provide the type of the signal in the RoutineControl request/response.
Multiplicity 1
Type EcucEnumerationParamDef
Range BOOLEAN Type of the signal is boolean.
FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 Type of the signal is sint16.
SINT16_N Type of the signal is sint16 array.
SINT32 Type of the signal is sint32.
SINT32_N Type of the signal is sint32 array.
SINT8 Type of the signal is sint8.
SINT8_N Type of the signal is sint8 array.
UINT16 Type of the signal is uint16.
UINT16_N Type of the signal is uint16 array.
UINT32 Type of the signal is uint32.
UINT32_N Type of the signal is uint32 array.
UINT8 Type of the signal is uint8.
UINT8_N Type of the signal is uint8 array.

626 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

VARIABLE_LENGTH Type of the signal is

uint8[DcmDspRoutineParameterSize].

This is only valid for the last signal and

when DcmDspRoutineSignalType is
set to VARIABLE_LENGTH.
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspArgument 0..1 This container contains the configuration (arguments) of
Scaling an alternative Diagnosis Representation. Out if this the
scaling between Diagnosis and ECU internal
representation and vice versa can be calculated.

10.2.5.18.10 DcmDspStartRoutineOut

SWS Item [ECUC_Dcm_00835]

Container Name DcmDspStartRoutineOut
Parent Container DcmDspStartRoutine
Description Provide description of output parameter of Start subservice for
RoutineControl service.
Configuration Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStartRoutineOut 1..* Provide description of a routine signal used in
Signal RoutineControl service.

The ordering defined via the index attribute of the

subcontainers in this list represents the order of the
dataOutN elements in the XXX_Start function call.

627 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspRoutineSignalPos: DcmDspStartRoutineOut: DcmDspRoutineParameterSize:

EcucIntegerParamDef EcucParamConfContainerDef EcucIntegerParamDef

lowerMultiplicity = 0 upperMultiplicity = 1 lowerMultiplicity = 0

upperMultiplicity = 1 lowerMultiplicity = 0 upperMultiplicity = 1
min = 0 min = 0
max = 65535 max = 65535 A UINT8:
A
+literal EcucEnumerationLiteralDef
+parameter
+parameter
+subContainer
+literal
UINT8_N:
DcmDspStartRoutineOutSignal: EcucEnumerationLiteralDef
EcucParamConfContainerDef
BOOLEAN:
upperMultiplicity = * EcucEnumerationLiteralDef
lowerMultiplicity = 1 +literal SINT8:
requiresIndex = true EcucEnumerationLiteralDef
+literal

DcmDspRoutineSignalType:
EcucEnumerationParamDef +literal SINT8_N:
EcucEnumerationLiteralDef
lowerMultiplicity = 1
upperMultiplicity = 1

+literal UINT16:
EcucEnumerationLiteralDef

+literal UINT16_N:
EcucEnumerationLiteralDef

+literal SINT16:
EcucEnumerationLiteralDef

+parameter
+literal SINT16_N:
EcucEnumerationLiteralDef

+literal UINT32:
EcucEnumerationLiteralDef

+literal UINT32_N:
EcucEnumerationLiteralDef

+literal SINT32:
EcucEnumerationLiteralDef

+literal SINT32_N:
EcucEnumerationLiteralDef

+literal
VARIABLE_LENGTH:
+literal +literal EcucEnumerationLiteralDef

FLOAT: FLOAT_N:
EcucEnumerationLiteralDef EcucEnumerationLiteralDef

DcmDspRoutineSignalEndianness: +literal LITTLE_ENDIAN:

EcucEnumerationParamDef EcucEnumerationLiteralDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1 +literal
OPAQUE:
EcucEnumerationLiteralDef

DcmDspArgumentScaling: +literal BIG_ENDIAN:

+subContainer EcucChoiceContainerDef EcucEnumerationLiteralDef

lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.49: DcmDspStartRoutineOut configuration overview

10.2.5.18.11 DcmDspStartRoutineOutSignal

SWS Item [ECUC_Dcm_00848]

628 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Container Name DcmDspStartRoutineOutSignal

Parent Container DcmDspStartRoutineOut
Description Provide description of a routine signal used in RoutineControl service.

The ordering defined via the index attribute of the subcontainers in this
list represents the order of the dataOutN elements in the XXX_Start
function call.

Attributes:
requiresIndex=true
Configuration Parameters

Name DcmDspRoutineParameterSize [ECUC_Dcm_00850]

Parent Container DcmDspStartRoutineOutSignal
Description Provide the size of a RoutineControl parameter in bytes
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalEndianness [ECUC_Dcm_01017]

Parent Container DcmDspStartRoutineOutSignal
Description Defines the endianness of the data belonging to a Routine Out Signal
for Start subfunction.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at
the lowest address.
LITTLE_ENDIAN Most significant byte shall be stored at
the highest address
OPAQUE Opaque data endianness
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value

629 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,

Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalPos [ECUC_Dcm_00867]

Parent Container DcmDspStartRoutineOutSignal
Description Provide the position of the signal in the RoutineControl
request/response. The position is defined in bits.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalType [ECUC_Dcm_00885]

Parent Container DcmDspStartRoutineOutSignal
Description Provide the type of the signal in the RoutineControl request/response.
Multiplicity 1
Type EcucEnumerationParamDef
Range BOOLEAN Type of the signal is boolean.
FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 Type of the signal is sint16.
SINT16_N Type of the signal is sint16 array.
SINT32 Type of the signal is sint32.
SINT32_N Type of the signal is sint32 array.
SINT8 Type of the signal is sint8.
SINT8_N Type of the signal is sint8 array.
UINT16 Type of the signal is uint16.
UINT16_N Type of the signal is uint16 array.
UINT32 Type of the signal is uint32.

630 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

UINT32_N Type of the signal is uint32 array.

UINT8 Type of the signal is uint8.
UINT8_N Type of the signal is uint8 array.
VARIABLE_LENGTH Type of the signal is
uint8[DcmDspRoutineParameterSize].

This is only valid for the last signal and

when DcmDspRoutineSignalType is
set to VARIABLE_LENGTH.
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspArgument 0..1 This container contains the configuration (arguments) of
Scaling an alternative Diagnosis Representation. Out if this the
scaling between Diagnosis and ECU internal
representation and vice versa can be calculated.

10.2.5.18.12 DcmDspStopRoutine

SWS Item [ECUC_Dcm_01022]

Container Name DcmDspStopRoutine
Parent Container DcmDspRoutine
Description Provides the configuration of Stop subservice for RoutineControl
service. Existence indicates that the StopRoutine in the RoutineControl
is supported.
Configuration Parameters

Name DcmDspRoutineInterfaceArgumentIntegrity [ECUC_Dcm_01184]

Parent Container DcmDspStopRoutine
Description Defines the value of ClientServerOperation.diagArgIntegrity for the
created C/S interface of this routine
Multiplicity 0..1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –

631 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspStopRoutineConfirmationEnabled [ECUC_Dcm_01095]

Parent Container DcmDspStopRoutine
Description Allows to enable/disable the confirmation function to indicate the
transmission of a response to a StopRoutine request
Multiplicity 0..1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspStopRoutineConfirmationFnc [ECUC_Dcm_01096]

Parent Container DcmDspStopRoutine
Description C-function to call if a transmission confirmation is needed by the issuer
(BSW module)
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

632 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspStopRoutineFnc [ECUC_Dcm_00752]

Parent Container DcmDspStopRoutine
Description Function name for request to application to stop a routine.
(Routine_Stop-function)

This parameter is related to the interface Xxx_Stop.

Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspStopRoutineRole [ECUC_Dcm_01145]

Parent Container DcmDspStopRoutine
Description Bitfield were each bit represents one dedicated role. A RoutineControl
with sub-function stopRoutine is granted access if the bit value is 1. If a
bit value is 0, the routine is not allowed for that role.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 4294967295
Default Value
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

633 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspStopRoutineCommonAuthorizationRef [ECUC_Dcm_01053]

Parent Container DcmDspStopRoutine
Description Reference to DcmDspCommonAuthorization

Common authorization configuration taken from the referenced

DcmDspStopRoutineCommonAuthorizationRef. If there is no
reference, no check on the commonly defined authorization conditions
shall be done to stop the routine.
Multiplicity 0..1
Type Reference to DcmDspCommonAuthorization
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStopRoutineIn 0..1 Provide description of input parameter of Stop
subservice for RoutineControl service.
DcmDspStopRoutineOut 0..1 Provide description of output parameter of Stop
subservice for RoutineControl service.

634 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspRoutine:
EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

+subContainer
DcmDspStopRoutineInSignal:
DcmDspStopRoutine: DcmDspStopRoutineIn:
EcucParamConfContainerDef
EcucParamConfContainerDef +subContainer EcucParamConfContainerDef +subContainer
upperMultiplicity = *
upperMultiplicity = 1 upperMultiplicity = 1
lowerMultiplicity = 1
lowerMultiplicity = 0 lowerMultiplicity = 0
requiresIndex = true

DcmDspStopRoutineOutSignal:
DcmDspStopRoutineOut:
EcucParamConfContainerDef
+subContainer EcucParamConfContainerDef +subContainer
upperMultiplicity = *
upperMultiplicity = 1
lowerMultiplicity = 1
lowerMultiplicity = 0
requiresIndex = true

DcmDspStopRoutineCommonAuthorizationRef: DcmDspCommonAuthorization:
+reference EcucReferenceDef +destination EcucParamConfContainerDef

lowerMultiplicity = 0 upperMultiplicity = *
upperMultiplicity = 1 lowerMultiplicity = 0

DcmDspStopRoutineFnc: EcucFunctionNameDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1
DcmDspStopRoutineRole:
EcucIntegerParamDef
+parameter
min = 0
max = 4294967295
lowerMultiplicity = 0
DcmDspStopRoutineConfirmationEnabled: upperMultiplicity = 1
EcucBooleanParamDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1
defaultValue = FALSE

DcmDspStopRoutineConfirmationFnc:
+parameter EcucFunctionNameDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspRoutineInterfaceArgumentIntegrity:
+parameter EcucBooleanParamDef

defaultValue = false
lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.50: DcmDspStopRoutine configuration overview

10.2.5.18.13 DcmDspStopRoutineIn

SWS Item [ECUC_Dcm_00832]

Container Name DcmDspStopRoutineIn
Parent Container DcmDspStopRoutine
Description Provide description of input parameter of Stop subservice for
RoutineControl service.
Configuration Parameters

635 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStopRoutineIn 1..* Provide description of a routine signal used in
Signal RoutineControl service.

The ordering defined via the index attribute of the

subcontainers in this list represents the order of the
dataInN elements in the XXX_Stop function call.

636 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspStopRoutineIn: DcmDspRoutineSignalPos: DcmDspRoutineParameterSize: DcmDspArgumentScaling:

EcucParamConfContainerDef EcucIntegerParamDef EcucIntegerParamDef EcucChoiceContainerDef

upperMultiplicity = 1 lowerMultiplicity = 1 lowerMultiplicity = 0 lowerMultiplicity = 0

lowerMultiplicity = 0 upperMultiplicity = 1 upperMultiplicity = 1 upperMultiplicity = 1
min = 0 min = 0
max = 65535 A max = 65535 A

+parameter +parameter
+subContainer
+subContainer

DcmDspStopRoutineInSignal:
EcucParamConfContainerDef

upperMultiplicity = * +literal UINT8:

lowerMultiplicity = 1 EcucEnumerationLiteralDef
requiresIndex = true BOOLEAN:
EcucEnumerationLiteralDef +literal
UINT8_N:
EcucEnumerationLiteralDef
+literal

DcmDspRoutineSignalType:
EcucEnumerationParamDef +literal SINT8:
EcucEnumerationLiteralDef
lowerMultiplicity = 1
upperMultiplicity = 1

+literal SINT8_N:
EcucEnumerationLiteralDef

+literal UINT16:
EcucEnumerationLiteralDef

+literal UINT16_N:
EcucEnumerationLiteralDef

+parameter +literal SINT16:

EcucEnumerationLiteralDef

+literal SINT16_N:
EcucEnumerationLiteralDef

+literal UINT32:
EcucEnumerationLiteralDef

+literal UINT32_N:
EcucEnumerationLiteralDef

+literal SINT32:
EcucEnumerationLiteralDef

+literal

SINT32_N:
+literal EcucEnumerationLiteralDef

FLOAT:
EcucEnumerationLiteralDef
+literal +literal

FLOAT_N: VARIABLE_LENGTH:
EcucEnumerationLiteralDef EcucEnumerationLiteralDef
LITTLE_ENDIAN:
+literal EcucEnumerationLiteralDef

DcmDspRoutineSignalEndianness: OPAQUE:
EcucEnumerationParamDef +literal EcucEnumerationLiteralDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1 +literal
BIG_ENDIAN:
EcucEnumerationLiteralDef

Figure 10.51: DcmDspRoutineStopIn configuration overview

10.2.5.18.14 DcmDspStopRoutineInSignal

SWS Item [ECUC_Dcm_00839]

637 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Container Name DcmDspStopRoutineInSignal

Parent Container DcmDspStopRoutineIn
Description Provide description of a routine signal used in RoutineControl service.

The ordering defined via the index attribute of the subcontainers in this
list represents the order of the dataInN elements in the XXX_Stop
function call.

Attributes:
requiresIndex=true
Configuration Parameters

Name DcmDspRoutineParameterSize [ECUC_Dcm_00841]

Parent Container DcmDspStopRoutineInSignal
Description Provide the size of a RoutineControl parameter in bytes
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalEndianness [ECUC_Dcm_01014]

Parent Container DcmDspStopRoutineInSignal
Description Defines the endianness of the data belonging to a Routine In Signal for
Stop subfunction.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at
the lowest address.
LITTLE_ENDIAN Most significant byte shall be stored at
the highest address
OPAQUE Opaque data endianness
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value

638 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,

Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalPos [ECUC_Dcm_00840]

Parent Container DcmDspStopRoutineInSignal
Description Provide the position of the signal in the RoutineControl
request/response. The position is defined in bits.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalType [ECUC_Dcm_00882]

Parent Container DcmDspStopRoutineInSignal
Description Provide the type of the signal in the RoutineControl request/response.
Multiplicity 1
Type EcucEnumerationParamDef
Range BOOLEAN Type of the signal is boolean.
FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 Type of the signal is sint16.
SINT16_N Type of the signal is sint16 array.
SINT32 Type of the signal is sint32.
SINT32_N Type of the signal is sint32 array.
SINT8 Type of the signal is sint8.
SINT8_N Type of the signal is sint8 array.
UINT16 Type of the signal is uint16.
UINT16_N Type of the signal is uint16 array.
UINT32 Type of the signal is uint32.
UINT32_N Type of the signal is uint32 array.
UINT8 Type of the signal is uint8.
UINT8_N Type of the signal is uint8 array.

639 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

VARIABLE_LENGTH Type of the signal is

uint8[DcmDspRoutineParameterSize].

This is only valid for the last signal and

when DcmDspRoutineSignalType is
set to VARIABLE_LENGTH.
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspArgument 0..1 This container contains the configuration (arguments) of
Scaling an alternative Diagnosis Representation. Out if this the
scaling between Diagnosis and ECU internal
representation and vice versa can be calculated.

10.2.5.18.15 DcmDspStopRoutineOut

SWS Item [ECUC_Dcm_00833]

Container Name DcmDspStopRoutineOut
Parent Container DcmDspStopRoutine
Description Provide description of output parameter of Stop subservice for
RoutineControl service.
Configuration Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStopRoutineOut 1..* Provide description of a routine signal used in
Signal RoutineControl service.

The ordering defined via the index attribute of the

subcontainers in this list represents the order of the
dataOutN elements in the XXX_Stop function call.

640 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDspStopRoutineOut:
EcucParamConfContainerDef

upperMultiplicity = 1
lowerMultiplicity = 0

+subContainer

DcmDspStopRoutineOutSignal: DcmDspRoutineSignalPos:
EcucParamConfContainerDef EcucIntegerParamDef
+parameter
upperMultiplicity = * lowerMultiplicity = 1 DcmDspRoutineParameterSize:
lowerMultiplicity = 1 upperMultiplicity = 1 EcucIntegerParamDef
requiresIndex = true min = 0
max = 65535 A lowerMultiplicity = 0
upperMultiplicity = 1
+parameter min = 0
max = 65535 A

+literal BOOLEAN:
DcmDspRoutineSignalType:
EcucEnumerationLiteralDef
EcucEnumerationParamDef

lowerMultiplicity = 1
upperMultiplicity = 1
+literal UINT8:
EcucEnumerationLiteralDef

+literal UINT8_N:
EcucEnumerationLiteralDef

+literal SINT8:
EcucEnumerationLiteralDef

+literal SINT8_N:
EcucEnumerationLiteralDef

+literal UINT16:
EcucEnumerationLiteralDef

+literal UINT16_N:
EcucEnumerationLiteralDef
+parameter
+literal SINT16:
EcucEnumerationLiteralDef
+literal SINT16_N:
EcucEnumerationLiteralDef

+literal UINT32:
EcucEnumerationLiteralDef
+literal UINT32_N:
EcucEnumerationLiteralDef

+literal SINT32:
EcucEnumerationLiteralDef
+literal SINT32_N:
EcucEnumerationLiteralDef

+literal VARIABLE_LENGTH:
EcucEnumerationLiteralDef

+literal
FLOAT_N:
+literal EcucEnumerationLiteralDef
FLOAT:
EcucEnumerationLiteralDef

DcmDspRoutineSignalEndianness: +literal LITTLE_ENDIAN:

EcucEnumerationParamDef EcucEnumerationLiteralDef
lowerMultiplicity = 0
upperMultiplicity = 1
+parameter +literal OPAQUE:
EcucEnumerationLiteralDef

+literal BIG_ENDIAN:
EcucEnumerationLiteralDef

DcmDspArgumentScaling:
+subContainer EcucChoiceContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.52: DcmDspStopRoutineOut configuration overview

10.2.5.18.16 DcmDspStopRoutineOutSignal

641 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

SWS Item [ECUC_Dcm_00842]

Container Name DcmDspStopRoutineOutSignal
Parent Container DcmDspStopRoutineOut
Description Provide description of a routine signal used in RoutineControl service.

The ordering defined via the index attribute of the subcontainers in this
list represents the order of the dataOutN elements in the XXX_Stop
function call.

Attributes:
requiresIndex=true
Configuration Parameters

Name DcmDspRoutineParameterSize [ECUC_Dcm_00844]

Parent Container DcmDspStopRoutineOutSignal
Description Provide the size of a RoutineControl parameter in bytes
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalEndianness [ECUC_Dcm_01015]

Parent Container DcmDspStopRoutineOutSignal
Description Defines the endianness of the data belonging to a Routine Out Signal
for Stop subfunction.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at
the lowest address.
LITTLE_ENDIAN Most significant byte shall be stored at
the highest address
OPAQUE Opaque data endianness
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value

642 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,

Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalPos [ECUC_Dcm_00843]

Parent Container DcmDspStopRoutineOutSignal
Description Provide the position of the signal in the RoutineControl
request/response. The position is defined in bits.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspRoutineSignalType [ECUC_Dcm_00883]

Parent Container DcmDspStopRoutineOutSignal
Description Provide the type of the signal in the RoutineControl request/response.
Multiplicity 1
Type EcucEnumerationParamDef
Range BOOLEAN Type of the signal is boolean.
FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 Type of the signal is sint16.
SINT16_N Type of the signal is sint16 array.
SINT32 Type of the signal is sint32.
SINT32_N Type of the signal is sint32 array.
SINT8 Type of the signal is sint8.
SINT8_N Type of the signal is sint8 array.
UINT16 Type of the signal is uint16.
UINT16_N Type of the signal is uint16 array.
UINT32 Type of the signal is uint32.
UINT32_N Type of the signal is uint32 array.
UINT8 Type of the signal is uint8.
UINT8_N Type of the signal is uint8 array.

643 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

VARIABLE_LENGTH Type of the signal is

uint8[DcmDspRoutineParameterSize].

This is only valid for the last signal and

when DcmDspRoutineSignalType is
set to VARIABLE_LENGTH.
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspArgument 0..1 This container contains the configuration (arguments) of
Scaling an alternative Diagnosis Representation. Out if this the
scaling between Diagnosis and ECU internal
representation and vice versa can be calculated.

10.2.5.19 Session Security and Modes

10.2.5.19.1 DcmDspSecurity

SWS Item [ECUC_Dcm_00764]

Container Name DcmDspSecurity
Parent Container DcmDsp
Description This container contains the configuration ( DSP parameter) for security
level configuration (per security level) Description This container
contains Rows of DcmDspSecurityRow
Configuration Parameters

Name DcmDspSecurityMaxAttemptCounterReadoutTime
[ECUC_Dcm_01101]
Parent Container DcmDspSecurity
Description Delay, in seconds, from startup (measured from the first call of the
Dcm_MainFunction()), allowed for all AttemptCounter values to be
obtained from the Application. Must be a multiple of the DcmTaskTime.

min: A value equal to the DcmTaskTime

Multiplicity 1
Type EcucFloatParamDef
Range ]0 .. 65535[
Default Value
Post-Build Variant false
Value

644 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,

Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspSecurityRow 0..31 Definition of a single Row of configuration for security
level configuration (per security level) The name of this
container is used to define the name of the R-Port
through which the DCM accesses the interface
SecurityAccess_{SecurityLevel}. The R-Port is named
SecurityAccess_{SecurityLevel} where {SecurityLevel} is
the name of the container DcmDspSecurityRow. If there
is no reference, no check of security level shall be done.

645 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Dcm: EcucModuleDef DcmDspSecurityRow: DcmDspSecuritySeedSize:

EcucParamConfContainerDef EcucIntegerParamDef
upperMultiplicity = 1
upperMultiplicity = 31 +parameter
lowerMultiplicity = 0 max = 4294967295
lowerMultiplicity = 0 min = 1
lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspSecurityKeySize:
+container EcucIntegerParamDef
+parameter
DcmConfigSet: max = 4294967295
EcucParamConfContainerDef min = 1
lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspSecurityADRSize:
+subContainer EcucIntegerParamDef
+parameter
DcmDsp: lowerMultiplicity = 0
EcucParamConfContainerDef upperMultiplicity = 1
min = 1
lowerMultiplicity = 0 max = 4294967295
upperMultiplicity = 1

DcmDspSecurityUsePort: +literalUSE_ASYNCH_CLIENT_SERVER:
+parameter EcucEnumerationParamDef EcucEnumerationLiteralDef

+subContainer lowerMultiplicity = 1
upperMultiplicity = 1
DcmDspSecurity:
USE_ASYNCH_FNC:
EcucParamConfContainerDef +literal
EcucEnumerationLiteralDef
lowerMultiplicity = 1 +subContainer
upperMultiplicity = 1

DcmDspSecurityGetAttemptCounterFnc:
EcucFunctionNameDef
+parameter
+parameter lowerMultiplicity = 0
upperMultiplicity = 1
DcmDspSecurityMaxAttemptCounterReadoutTime:
EcucFloatParamDef

min = 0
max = 65535 DcmDspSecuritySetAttemptCounterFnc:
lowerMultiplicity = 1 EcucFunctionNameDef
upperMultiplicity = 1 +parameter
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspSecurityAttemptCounterEnabled:
+parameter EcucBooleanParamDef

DcmDspSecurityLevel: upperMultiplicity = 1
EcucIntegerParamDef lowerMultiplicity = 1

max = 63 +parameter
min = 1
lowerMultiplicity = 1 DcmDspSecurityGetSeedFnc:
upperMultiplicity = 1 EcucFunctionNameDef
+parameter
symbolicNameValue = true
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspSecurityNumAttDelay:
EcucIntegerParamDef
+parameter DcmDspSecurityCompareKeyFnc:
min = 1 +parameter EcucFunctionNameDef
max = 255
lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = 1

DcmDspSecurityDelayTime: DcmDspSecurityDelayTimeOnBoot:
EcucFloatParamDef EcucFloatParamDef
+parameter +parameter
min = 0 min = 0
lowerMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = 1
max = 65535 max = 65535

Figure 10.53: DcmDspSecurity configuration overview

10.2.5.19.2 DcmDspSecurityRow

SWS Item [ECUC_Dcm_00759]

646 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Container Name DcmDspSecurityRow

Parent Container DcmDspSecurity
Description Definition of a single Row of configuration for security level
configuration (per security level) The name of this container is used to
define the name of the R-Port through which the DCM accesses the
interface SecurityAccess_{SecurityLevel}. The R-Port is named
SecurityAccess_{SecurityLevel} where {SecurityLevel} is the name of
the container DcmDspSecurityRow. If there is no reference, no check
of security level shall be done.
Configuration Parameters

Name DcmDspSecurityADRSize [ECUC_Dcm_00725]

Parent Container DcmDspSecurityRow
Description Size in bytes of the AccessDataRecord used in GetSeed
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 4294967295
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspSecurityAttemptCounterEnabled [ECUC_Dcm_01050]

Parent Container DcmDspSecurityRow
Description This configuration parameter controls the existence of the APIs to set /
get the attempt counter values towards application
(Xxx_SetSecurityAttemptCounter() /
Xxx_GetSecurityAttemptCounter()). In case of enabled, the security
attempt counter values are passed to application, whenever there is a
change in the value. This allows storing the values in nonvolatile RAM
and restoring them at ECU startup.
Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –

647 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Scope / Dependency scope: ECU

Name DcmDspSecurityCompareKeyFnc [ECUC_Dcm_00969]

Parent Container DcmDspSecurityRow
Description Function name to request the result of a key comparison.

Parameter is only relevant if DcmDspSecurityUsePort=="USE_

ASYNCH_FNC". This parameter is related to the interface
Xxx_CompareKey.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspSecurityDelayTime [ECUC_Dcm_00757]

Parent Container DcmDspSecurityRow
Description Delay time after failed security access in seconds.

This is started after DcmDspSecurityNumAttDelay number of failed

security accesses.

min: A negative value is not allowed.

Multiplicity 1
Type EcucFloatParamDef
Range [0 .. 65535]
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

648 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspSecurityDelayTimeOnBoot [ECUC_Dcm_00726]

Parent Container DcmDspSecurityRow
Description Value of the delay timer in case of ’power on’ in seconds. This delay
indicates the time at ECU boot power-on time during which the Dcm
does not accept a security access.

min: A negative value is not allowed.

Multiplicity 1
Type EcucFloatParamDef
Range [0 .. 65535]
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspSecurityGetAttemptCounterFnc [ECUC_Dcm_01048]

Parent Container DcmDspSecurityRow
Description Function name to request the value of an attempt counter. This
parameter is related to the interface Xxx_ GetSecurityAttemptCounter.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspSecurityGetSeedFnc [ECUC_Dcm_00968]

Parent Container DcmDspSecurityRow
Description Callout function name used to request a seed. This parameter is
related to the interface Xxx_GetSeed.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression

649 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Post-Build Variant false

Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspSecurityKeySize [ECUC_Dcm_00760]

Parent Container DcmDspSecurityRow
Description size of the security key (in Bytes).
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 4294967295
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspSecurityLevel [ECUC_Dcm_00754]

Parent Container DcmDspSecurityRow
Description Value of Security level. The locked state cannot be configured explicitly.

1,2,3...63: configuration dependent - Conversion formula to calculate

SecurityLevel out of tester requested

SecurityAccessType parameter: SecurityLevel = (SecurityAccessType

(requestSeed) + 1) / 2

Type: Dcm_SecLevelType
Multiplicity 1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 1 .. 63
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –

650 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Scope / Dependency scope: local

Name DcmDspSecurityNumAttDelay [ECUC_Dcm_00762]

Parent Container DcmDspSecurityRow
Description Number of failed security accesses after which the delay time is
activated
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspSecuritySeedSize [ECUC_Dcm_00755]

Parent Container DcmDspSecurityRow
Description size of the security seed (in Bytes).
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 4294967295
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspSecuritySetAttemptCounterFnc [ECUC_Dcm_01049]

Parent Container DcmDspSecurityRow
Description Function name to set the value of an attempt counter. This parameter
is related to the interface Xxx_ SetSecurityAttemptCounter.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value

651 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,

Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspSecurityUsePort [ECUC_Dcm_00967]

Parent Container DcmDspSecurityRow
Description Defines which kind of interface shall be used for security access.
Multiplicity 1
Type EcucEnumerationParamDef
Range USE_ASYNCH_CLIENT_ The DCM will access the data using an
SERVER R-Port requiring a asynchronous
ClientServertInterface
SecurityAccess_{SecurityLevel}.

The R-Port is described in

DcmDspSecurityRow description.
USE_ASYNCH_FNC The DCM will access the data using
the functions that are defined in the
parameters
DcmDspSecurityGetSeedFnc and
DcmDspSecurityCompareKeyFnc as
well as the functions defined in DcmD-
spSecurityGetAttemptCounterFnc and
DcmDspSecuritySetAttemptCoun-
terFnc, if enabled by the parameter
DcmDspSecurityAttemptCounterEn-
abled.

DCM_E_PENDING return is allowed

and OpStatus is existing as IN
parameter.
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

No Included Containers

10.2.5.19.3 DcmDspSession

652 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

SWS Item [ECUC_Dcm_00769]

Container Name DcmDspSession
Parent Container DcmDsp
Description Parent container holding single rows to configure particular sessions
Configuration Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspSessionRow 0..31 This container holds all parameters needed to configure
a single session

SWS Item [ECUC_Dcm_00764]

Container Name DcmDspSecurity
Parent Container DcmDsp
Description This container contains the configuration ( DSP parameter) for security
level configuration (per security level) Description This container
contains Rows of DcmDspSecurityRow
Configuration Parameters

Name DcmDspSecurityMaxAttemptCounterReadoutTime
[ECUC_Dcm_01101]
Parent Container DcmDspSecurity
Description Delay, in seconds, from startup (measured from the first call of the
Dcm_MainFunction()), allowed for all AttemptCounter values to be
obtained from the Application. Must be a multiple of the DcmTaskTime.

min: A value equal to the DcmTaskTime

Multiplicity 1
Type EcucFloatParamDef
Range ]0 .. 65535[
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspSecurityRow 0..31 Definition of a single Row of configuration for security
level configuration (per security level) The name of this
container is used to define the name of the R-Port
through which the DCM accesses the interface
SecurityAccess_{SecurityLevel}. The R-Port is named
SecurityAccess_{SecurityLevel} where {SecurityLevel} is
the name of the container DcmDspSecurityRow. If there
is no reference, no check of security level shall be done.

653 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDsp: DcmDspSessionRow: DcmDspSessionLevel:

EcucParamConfContainerDef EcucParamConfContainerDef EcucIntegerParamDef

lowerMultiplicity = 0 upperMultiplicity = 31 +parameter max = 126

upperMultiplicity = 1 lowerMultiplicity = 0 min = 1
lowerMultiplicity = 1
upperMultiplicity = 1
symbolicNameValue = true

+subContainer
DcmDspSessionP2StarServerMax:
DcmDspSession:
EcucFloatParamDef
EcucParamConfContainerDef
+parameter
+subContainer min = 0
lowerMultiplicity = 1
lowerMultiplicity = 1
upperMultiplicity = 1
upperMultiplicity = 1
max = 100

DcmDspSessionP2ServerMax:
EcucFloatParamDef
+parameter
min = 0
lowerMultiplicity = 1
upperMultiplicity = 1
max = 1

+parameter

DcmDspSessionForBoot: +literal DCM_NO_BOOT:

EcucEnumerationParamDef EcucEnumerationLiteralDef

lowerMultiplicity = 1
upperMultiplicity = 1

+literal DCM_OEM_BOOT:
EcucEnumerationLiteralDef

+literal DCM_SYS_BOOT:
EcucEnumerationLiteralDef

+literal DCM_OEM_BOOT_RESPAPP:
EcucEnumerationLiteralDef

+literal DCM_SYS_BOOT_RESPAPP:
EcucEnumerationLiteralDef

Figure 10.54: DcmDspSession configuration overview

10.2.5.19.4 DcmDspSessionRow

SWS Item [ECUC_Dcm_00767]

Container Name DcmDspSessionRow
Parent Container DcmDspSession
Description This container holds all parameters needed to configure a single
session
Configuration Parameters

654 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspSessionForBoot [ECUC_Dcm_00815]

Parent Container DcmDspSessionRow
Description This parameter defines whether this diagnostic session allows to jump
to Bootloader (OEM Bootloader or System Supplier Bootloader) and
determines, from which unit the final response will be sent. If this
diagnostic session doesn’t allow to jump to Bootloader the value
DCM_NO_BOOT shall be chosen.
Multiplicity 1
Type EcucEnumerationParamDef
Range DCM_NO_BOOT This diagnostic session doesn’t allow
to jump to Bootloader.
DCM_OEM_BOOT This diagnostic session allows to jump
to OEM Bootloader and bootloader
sends final response.
DCM_OEM_BOOT_RESP This diagnostic session allows to jump
APP to OEM Bootloader and application
sends final response.
DCM_SYS_BOOT This diagnostic session allows to jump
to System Supplier Bootloader and
bootloader sends final response.
DCM_SYS_BOOT_RESP This diagnostic session allows to jump
APP to System Supplier Bootloader and
application sends final response.
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspSessionLevel [ECUC_Dcm_00765]

Parent Container DcmDspSessionRow
Description subFunction value of the DiagnosticSession.

0, 127 and all values above 127 are reserved by ISO

Multiplicity 1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 1 .. 126
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

655 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspSessionP2ServerMax [ECUC_Dcm_00766]

Parent Container DcmDspSessionRow
Description This is the session value for P2ServerMax in seconds (per Session).
The AUTOSAR configuration standard is to use SI units, so this
parameter is defined as a float value in seconds. DCM configuration
tools must convert this float value to the appropriate value format for
the use in the software implementation of DCM. This value is reported
to the tester within the response to the ’Session Control’ service.
Multiplicity 1
Type EcucFloatParamDef
Range [0 .. 1]
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspSessionP2StarServerMax [ECUC_Dcm_00768]

Parent Container DcmDspSessionRow
Description This is the session value for P2*ServerMax in seconds (per Session).
The AUTOSAR configuration standard is to use SI units, so this
parameter is defined as a float value in seconds. DCM configuration
tools must convert this float value to the appropriate value format for
the use in the software implementation of DCM. This value is reported
to the tester within the response to the ’Session Control’ service.
Multiplicity 1
Type EcucFloatParamDef
Range [0 .. 100]
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

No Included Containers

10.2.5.19.5 DcmModeCondition

SWS Item [ECUC_Dcm_00928]

Container Name DcmModeCondition
Parent Container DcmProcessingConditions

656 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Description This container contains the configuration of a mode condition or an

environmental conditions which can be used as argument in
DcmModeRules.

One DcmModeCondition shall contain either one DcmSwcModeRef or

one DcmBswModeRef or one DcmSwcSRDataElementRef.

Please note that the Dcm acts as well as mode manager. Therefore
the references DcmSwcModeRef or one DcmBswModeRef. might
point to provided ModeDeclarationGroupPrototypes of the Dcm itself
as well as to provided ModeDeclarationGroupPrototypes of other Bsw
Modules or software components.

In case of a configured DcmSwcModeRef or DcmBswModeRef only

the DcmConditionType DCM_EQUALS or DCM_EQUALS_NOT are
applicable.

In case of DcmSwcSRDataElementRef all literals of DcmConditionType

are possible.
Configuration Parameters

Name DcmConditionType [ECUC_Dcm_00929]

Parent Container DcmModeCondition
Description This parameter specifies what kind of comparison that is made for the
evaluation of the mode condition.
Multiplicity 1
Type EcucEnumerationParamDef
Range DCM_EQUALS
DCM_EQUALS_NOT
DCM_GREATER_OR_EQ
UAL
DCM_GREATER_THAN
DCM_LESS_OR_EQUAL
DCM_LESS_THAN
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

657 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmBswModeRef [ECUC_Dcm_00931]

Parent Container DcmModeCondition
Description This parameter references a mode of a
ModeDeclarationGroupPrototype provided by a Basic Software Module
used for the condition.

Please note that such ModeDeclarationGroupPrototype are owned by

a Basic Software Module Description in the role providedModeGroup.
Multiplicity 0..1
Type Instance reference to MODE-DECLARATION context: MODE-DECLA
RATION-GROUP-PROTOTYPE
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DcmModeConditionCertificateCompareElementRef
[ECUC_Dcm_01179]
Parent Container DcmModeCondition
Description Reference to a certificate data element that provides the compare
value.
Multiplicity 0..1
Type Symbolic name reference to KeyMCertificateElement
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

658 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmSwcModeRef [ECUC_Dcm_00930]

Parent Container DcmModeCondition
Description This parameter references a mode in a particular mode request port of
a software component that is used for the condition.
Multiplicity 0..1
Type Instance reference to MODE-DECLARATION context: ROOT-SW-CO
MPOSITION-PROTOTYPE SW-COMPONENT-PROTOTYPE P-PORT-
PROTOTYPE MODE-DECLARATION-GROUP-PROTOTYPE
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DcmSwcSRDataElementRef [ECUC_Dcm_001037]

Parent Container DcmModeCondition
Description Reference to environmental conditions. It is possible to reference a
S/R Receiver-Port to read physical values and compare (equal,
greater, less,...) them with a configured value that is defined by
DcmSwcDataElementValue.
Multiplicity 0..1
Type Choice reference to [DcmDspExternalSRDataElement-
Class,DcmDspPidService01ExternalSRDataElementClass]
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Included Containers
Container Name Multiplicity Scope / Dependency
DcmSwcDataElement 1 This container contains the configuration of a compare
Value value.

659 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

10.2.5.19.6 DcmSwcDataElementValue

SWS Item [ECUC_Dcm_01123]

Container Name DcmSwcDataElementValue
Parent Container DcmModeCondition
Description This container contains the configuration of a compare value.
Configuration Parameters

Container Choices
Container Name Multiplicity Scope / Dependency
DcmSwcDataElement 0..1 This container contains the configuration of a array
Array compare value.
DcmSwcDataElement 0..1 This container contains the configuration of a primitive
Primitive compare value.

10.2.5.19.7 DcmSwcDataElementPrimitive

SWS Item [ECUC_Dcm_01124]

Container Name DcmSwcDataElementPrimitive
Parent Container DcmSwcDataElementValue
Description This container contains the configuration of a primitive compare value.
Configuration Parameters

Name DcmSwcDataElementPrimitiveValue [ECUC_Dcm_01126]

Parent Container DcmSwcDataElementPrimitive
Description Primitive compare value.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 ..
18446744073709551615
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency

No Included Containers

10.2.5.19.8 DcmSwcDataElementArray

SWS Item [ECUC_Dcm_01125]

Container Name DcmSwcDataElementArray

660 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Parent Container DcmSwcDataElementValue

Description This container contains the configuration of a array compare value.
Configuration Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmSwcDataElement 0..* This container contains the configuration of a array
ArrayElement element compare value.

10.2.5.19.9 DcmSwcDataElementArrayElement

SWS Item [ECUC_Dcm_01129]

Container Name DcmSwcDataElementArrayElement
Parent Container DcmSwcDataElementArray
Description This container contains the configuration of a array element compare
value.
Configuration Parameters

Name DcmSwcDataElementArrayElementIndex [ECUC_Dcm_01127]

Parent Container DcmSwcDataElementArrayElement
Description Index to an element of the compare value array.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 ..
18446744073709551615
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency

Name DcmSwcDataElementArrayElementValue [ECUC_Dcm_01128]

Parent Container DcmSwcDataElementArrayElement
Description Value of an array element compare value.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 ..
18446744073709551615
Default Value
Post-Build Variant false
Value

661 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency

No Included Containers

10.2.5.19.10 DcmModeRule

SWS Item [ECUC_Dcm_00925]

Container Name DcmModeRule
Parent Container DcmProcessingConditions
Description This container contains the configuration of a mode rule which
represents a logical expression with DcmModeConditions or other
DcmModeRules as arguments.

All arguments are processed with the operator defined by

DcmLogicalOperator, for instance: Argument_A AND Argument_B
AND Argument_C
Configuration Parameters

Name DcmLogicalOperator [ECUC_Dcm_00926]

Parent Container DcmModeRule
Description This parameter specifies the logical operator to be used in the logical
expression. If the expression only consists of a single condition this
parameter shall not be used.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range DCM_AND
DCM_OR
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

662 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmModeRuleNrcValue [ECUC_Dcm_00949]

Parent Container DcmModeRule
Description Optional parameter which defines the NRC to be sent in case the
mode rule condition is not valid.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 255
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmArgumentRef [ECUC_Dcm_00927]

Parent Container DcmModeRule
Description This is a choice reference either to a mode condition or a an other
mode rule serving as sub-expression.

Attributes:
requiresIndex=true
Multiplicity 1..*
Type Choice reference to [DcmModeCondition,DcmModeRule]
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

663 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

No Included Containers
DcmDspComControlCommunicationReEnableModeRuleRef: DcmModeRule:
EcucReferenceDef +destination EcucParamConfContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = *

DcmDspCommonAuthorizationModeRuleRef:
EcucReferenceDef +destination

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspWriteMemoryRangeModeRuleRef:
EcucReferenceDef +destination

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDidReadModeRuleRef: EcucReferenceDef
+destination
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDsdSidTabModeRuleRef: EcucReferenceDef
+destination
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspControlDTCSettingReEnableModeRuleRef:
EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspReadMemoryRangeModeRuleRef:
EcucReferenceDef +destination

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspClearDTCModeRuleRef:
EcucReferenceDef +destination

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDidWriteModeRuleRef: EcucReferenceDef
+destination
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDidControlModeRuleRef:
EcucReferenceDef +destination

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDsdSubServiceModeRuleRef:
EcucReferenceDef +destination

lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.55: DcmModeRuleUsage configuration overview

10.2.5.20 DcmDspVehInfo

664 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

SWS Item [ECUC_Dcm_00630]

Container Name DcmDspVehInfo
Parent Container DcmDsp
Description This container contains the configuration (parameters) for one single
VehicleInfoType of service $09
Configuration Parameters

Name DcmDspVehInfoInfoType [ECUC_Dcm_00631]

Parent Container DcmDspVehInfo
Description value of InfoType.

Within each DcmConfigSet all DcmDspVehInfoInfoType values shall be

unique.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspVehInfoNODIProvResp [ECUC_Dcm_01051]

Parent Container DcmDspVehInfo
Description Indicate the Dcm, which side is responsible to fill the number of data
items (NODI), Dcm or the provider of the InfoType data. In case the
responsibility is on provider side, only one DcmDspVehInfoData
container is allowed.
• true: Provider is responsible for providing the number of data
items parameter
• false or not existing: Dcm is responsible for providing the
number of data items parameter

Multiplicity 0..1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

665 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspVehInfoData 1..* Data Item of an InfoType; ShortName is post-fix of the
port interface name.

DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspVehInfo: DcmDspVehInfoInfoType:
EcucParamConfContainerDef EcucIntegerParamDef
+parameter
upperMultiplicity = * lowerMultiplicity = 1
lowerMultiplicity = 0 upperMultiplicity = 1
min = 0
max = 255

DcmDspVehInfoDataReadFnc:
DcmDspVehInfoData: +parameter EcucFunctionNameDef
EcucParamConfContainerDef
lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = 1
lowerMultiplicity = 1

DcmDspVehInfoDataSize:
EcucIntegerParamDef
+parameter lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
+subContainer max = 255

DcmDspVehInfoDataOrder:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
max = 255

DcmDspVehInfoDataUsePort:
+parameter EcucBooleanParamDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspVehInfoNODIProvResp:
EcucBooleanParamDef
+parameter
upperMultiplicity = 1
lowerMultiplicity = 0
defaultValue = false

Figure 10.56: DcmDspVehInfo configuration overview

10.2.5.21 DcmDspVehInfoData

SWS Item [ECUC_Dcm_00888]

Container Name DcmDspVehInfoData
Parent Container DcmDspVehInfo
Description Data Item of an InfoType; ShortName is post-fix of the port interface
name.
Configuration Parameters

666 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspVehInfoDataOrder [ECUC_Dcm_00891]

Parent Container DcmDspVehInfoData
Description Defines the order of the data item in the InfoType; values: 0..255; first
data item having the order number 0; the next 1 and so on. The
configuration of order needs to be unique per InfoType.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspVehInfoDataReadFnc [ECUC_Dcm_00889]

Parent Container DcmDspVehInfoData
Description Callout function name for reading InfoType data item. Only required in
case parameter ’DcmDspVehInfoDataUsePort’ is set to ’false’
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspVehInfoDataSize [ECUC_Dcm_00890]

Parent Container DcmDspVehInfoData
Description Size in bytes of the InfoType data item.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value

667 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspVehInfoDataUsePort [ECUC_Dcm_00727]

Parent Container DcmDspVehInfoData
Description When this parameter is set to true the DCM will access the Data using
an R-Port requiring a PortInterface IInfotypeServices_{VehInfoData}.
The R-Port is named InfotypeServices_{VehInfoData} where
{VEHINFODATA} is the name of the container DcmDspVehInfoData. In
that case, the DcmDspVehInfoDataReadFnc is ignored and the RTE
APIs are used.

When this parameter is set to false, the DCM calls the function defined
in DcmDspVehInfoDataReadFnc.
Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

No Included Containers

10.2.5.22 DcmDspPeriodicTransmission

SWS Item [ECUC_Dcm_00957]

Container Name DcmDspPeriodicTransmission
Parent Container DcmDsp
Description This container contains the configuration (parameters) for Periodic
Transmission Scheduler.
Configuration Parameters

Name DcmDspMaxPeriodicDidScheduler [ECUC_Dcm_00962]

Parent Container DcmDspPeriodicTransmission
Description Defines the maximum number of periodicDataIdentifiers that can be
scheduled concurrently.
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 255

668 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspPeriodicTransmissionFastRate [ECUC_Dcm_00960]

Parent Container DcmDspPeriodicTransmission
Description This parameter give the transmission rate of the requested
periodicDataIdentifiers to be used if the parameter transmissionMode
given in the ReadDataByPeriodicID request is equal to 0x03
("sendAtFastRate"). This parameter value in seconds have to be
configured as a multiple of DcmTaskTime.

min: A negative value and zero is not allowed.

Multiplicity 0..1
Type EcucFloatParamDef
Range [1E-4 .. 1]
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspPeriodicTransmissionMaxPeriodicFastTransmissions
[ECUC_Dcm_01182]
Parent Container DcmDspPeriodicTransmission
Description Defines the maximum number of periodic connections used for fast
transmission.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value

669 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DcmDspPeriodicTransmissionMaxPeriodicMediumTransmissions
[ECUC_Dcm_01181]
Parent Container DcmDspPeriodicTransmission
Description Defines the maximum number of periodic connections used for
medium transmission.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DcmDspPeriodicTransmissionMaxPeriodicSlowTransmissions
[ECUC_Dcm_01183]
Parent Container DcmDspPeriodicTransmission
Description Defines the maximum number of periodic connections used for slow
transmission.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

670 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspPeriodicTransmissionMediumRate [ECUC_Dcm_00959]

Parent Container DcmDspPeriodicTransmission
Description This parameter give the transmission rate of the requested
periodicDataIdentifiers to be used if the parameter transmissionMode
given in the ReadDataByPeriodicID request is equal to 0x02
("sendAtMediumRate"). This parameter value in seconds have to be
configured as a multiple of DcmTaskTime.

min: A negative value and zero is not allowed.

Multiplicity 0..1
Type EcucFloatParamDef
Range [1E-4 .. 1]
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmDspPeriodicTransmissionSchedulerType [ECUC_Dcm_01180]

Parent Container DcmDspPeriodicTransmission
Description Defines the used scheduler type according to ISO 14229-1:2018 for
read data by periodic identifier.
Multiplicity 1
Type EcucEnumerationParamDef
Range SCHEDULER_TYPE1 Selects the scheduler type#1 of ISO
14229-1:2018
SCHEDULER_TYPE2 Selects the scheduler type#2 of ISO
14229-1:2018
Default Value SCHEDULER_TYPE1
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

671 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmDspPeriodicTransmissionSlowRate [ECUC_Dcm_00958]

Parent Container DcmDspPeriodicTransmission
Description This parameter give the transmission rate of the requested
periodicDataIdentifiers to be used if the parameter transmissionMode
given in the ReadDataByPeriodicID request is equal to 0x01
("sendAtSlowRate"). This parameter value in seconds have to be
configured as a multiple of DcmTaskTime.

min: A negative value and zero is not allowed.

Multiplicity 0..1
Type EcucFloatParamDef
Range [1E-4 .. 1]
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

672 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

No Included Containers
DcmDsp: EcucParamConfContainerDef DcmDspPeriodicTransmission:
DcmDspPeriodicTransmissionSlowRate:
EcucParamConfContainerDef
lowerMultiplicity = 0 EcucFloatParamDef
upperMultiplicity = 1 lowerMultiplicity = 0 +parameter
min = 0.0001
upperMultiplicity = 1
max = 1
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspPeriodicTransmissionMediumRate:
EcucFloatParamDef
+parameter
min = 0.0001
max = 1
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspPeriodicTransmissionFastRate:
EcucFloatParamDef
+parameter
min = 0.0001
max = 1
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspMaxPeriodicDidScheduler:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
min = 1
max = 255

+subContainer
DcmDspPeriodicTransmissionSchedulerType:
EcucEnumerationParamDef

+parameter defaultValue = SCHEDULER_TYPE1

lowerMultiplicity = 1
upperMultiplicity = 1

+literal +literal

SCHEDULER_TYPE2: SCHEDULER_TYPE1:
EcucEnumerationLiteralDef EcucEnumerationLiteralDef

DcmDspPeriodicTransmissionMaxPeriodicFastTransmissions:
EcucIntegerParamDef
+parameter
min = 0
max = 255
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspPeriodicTransmissionMaxPeriodicMediumTransmissions:
EcucIntegerParamDef
+parameter
min = 0
max = 255
lowerMultiplicity = 0
upperMultiplicity = 1

+parameter
DcmDspPeriodicTransmissionMaxPeriodicSlowTransmissions:
EcucIntegerParamDef

min = 0
max = 255
lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.57: DcmDspPeriodicTransmission configuration overview

10.2.5.23 DcmDspClearDTC

SWS Item [ECUC_Dcm_01064]

673 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Container Name DcmDspClearDTC

Parent Container DcmDsp
Description This container contains the configuration for the Clear DTC service.
Configuration Parameters

Name DcmDspClearDTCCheckFnc [ECUC_Dcm_01066]

Parent Container DcmDspClearDTC
Description Callback function for condition check, manufacturer / supplier specific
checks on the groupOfDTC, which is requested to clear.

This parameter is related to the interface : Xxx_ClearDTCCheckFnc.

Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmDspClearDTCModeRuleRef [ECUC_Dcm_01065]

Parent Container DcmDspClearDTC
Description Reference to DcmModeRule

Mode rule which controls to clear the DTCs. If there is no reference, no

check of the mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE,
Configuration Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –

674 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Scope / Dependency scope: ECU

No Included Containers
DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspClearDTC: DcmDspClearDTCModeRuleRef: DcmModeRule:

EcucParamConfContainerDef +reference EcucReferenceDef +destination EcucParamConfContainerDef
upperMultiplicity = 1 lowerMultiplicity = 0 lowerMultiplicity = 1
lowerMultiplicity = 0 upperMultiplicity = 1 upperMultiplicity = *

DcmDspClearDTCCheckFnc:
+parameter EcucFunctionNameDef

lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.58: DcmDspClearDTC configuration overview

10.2.6 DcmGeneral

SWS Item [ECUC_Dcm_00822]

Container Name DcmGeneral
Parent Container Dcm
Description Contains general configuration parameters valid for the entire Dcm
module.
Configuration Parameters

Name DcmDDDIDStorage [ECUC_Dcm_00971]

Parent Container DcmGeneral
Description This configuration switch defines, whether DDDID definition is stored
non-volatile or not.

true: DDDID are stored non-volatile false: DDDID are only maintained
volatile
Multiplicity 0..1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –

675 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Value Configuration Pre-compile time X All Variants

Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DcmDevErrorDetect [ECUC_Dcm_00823]

Parent Container DcmGeneral
Description Switches the development error detection and notification on or off.
• true: detection and notification is enabled.
• false: detection and notification is disabled.

Multiplicity 1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DcmEnableSecurityEventReporting [ECUC_Dcm_01187]

Parent Container DcmGeneral
Description Switches the reporting of security events to the IdsM: - true: reporting
is enabled. - false: reporting is disabled.

Tags:
atp.Status=draft
Multiplicity 1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmHeaderFileInclusion [ECUC_Dcm_01019]

Parent Container DcmGeneral
Description Name of the header file(s) to be included by the Dcm module
containing the used C-callback declarations.
Multiplicity 0..*
Type EcucStringParamDef
Default Value

676 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Regular Expression [a-zA-Z0-9_]([a-zA-Z0-9\._])*

Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name DcmRespondAllRequest [ECUC_Dcm_00600]

Parent Container DcmGeneral
Description If set to FALSE the Dcm will not respond to diagnostic request that
contains a service ID which is in the range from 0x40 to 0x7F or in the
range from 0xC0 to 0xFF (Response IDs).
Multiplicity 1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

677 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmTaskTime [ECUC_Dcm_00820]

Parent Container DcmGeneral
Description Allow to configure the time for the periodic cyclic task. Please note:
This configuration value shall be equal to the value in the RTE module.

The AUTOSAR configuration standard is to use SI units, so this

parameter is defined as float value in seconds. Dcm configuration tools
must convert this float value to the appropriate value format for the use
in the software implementation of Dcm.

min: A negative value and zero is not allowed.

upperMultiplicity: Exactly one TaskTime must be specified per

configuration.

lowerMultiplicity: Exactly one TaskTime must be specified per

configuration.
Multiplicity 1
Type EcucFloatParamDef
Range ]0 .. INF[
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE,
Class VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

Name DcmVersionInfoApi [ECUC_Dcm_00821]

Parent Container DcmGeneral
Description Preprocessor switch to enable or disable the output Version info of the
functionality.
Multiplicity 1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

678 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DcmVinRef [ECUC_Dcm_00984]

Parent Container DcmGeneral
Description Reference to the Did containing the VIN Information.

This parameter is needed for function Dcm_GetVin

Multiplicity 0..1
Type Reference to DcmDspDid
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Included Containers
Container Name Multiplicity Scope / Dependency
DcmSecurityEventRefs 0..1 Container for the references to IdsMEvent elements
representing the security events that the Dcm module
shall report to the IdsM in case the coresponding
security related event occurs (and if
DcmEnableSecurityEventReporting is set to "true"). The
standardized security events in this container can be
extended by vendor-specific security events.

Tags:
atp.Status=draft

679 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmDevErrorDetect: EcucBooleanParamDef DcmGeneral: DcmVersionInfoApi: EcucBooleanParamDef

+parameter EcucParamConfContainerDef +parameter
upperMultiplicity = 1 upperMultiplicity = 1
lowerMultiplicity = 1 lowerMultiplicity = 1 lowerMultiplicity = 1
defaultValue = false upperMultiplicity = 1 defaultValue = false

DcmVinRef: EcucReferenceDef DcmTaskTime: EcucFloatParamDef

+reference
lowerMultiplicity = 0 +parameter min = 0
upperMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1
max = INF
+destination

DcmDspDid: EcucParamConfContainerDef
DcmRespondAllRequest: EcucBooleanParamDef
upperMultiplicity = * +parameter
lowerMultiplicity = 0 upperMultiplicity = 1
lowerMultiplicity = 1

DcmDDDIDStorage: EcucBooleanParamDef DcmHeaderFileInclusion: EcucStringParamDef

+parameter
upperMultiplicity = 1 +parameter lowerMultiplicity = 0
lowerMultiplicity = 0 upperMultiplicity = *
defaultValue = false regularExpression = [a-zA-Z0-9_]([a-zA-Z0-9\._])*

+parameter DcmEnableSecurityEventReporting:
EcucBooleanParamDef

defaultValue = false

DcmSecurityEventRefs:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.59: DcmGeneral configuration overview

10.2.6.1 DcmSecurityEventRefs

SWS Item [ECUC_Dcm_01188]

Container Name DcmSecurityEventRefs
Parent Container DcmGeneral
Description Container for the references to IdsMEvent elements representing the
security events that the Dcm module shall report to the IdsM in case
the coresponding security related event occurs (and if
DcmEnableSecurityEventReporting is set to "true"). The standardized
security events in this container can be extended by vendor-specific
security events.

Tags:
atp.Status=draft
Post-Build Variant false
Multiplicity
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Configuration Parameters

680 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DIAG_SEV_AUTHENTICATION_SUCCESSFUL [ECUC_Dcm_01197]

Parent Container DcmSecurityEventRefs
Description Successfully authenticated (via Authentication $29)

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DIAG_SEV_CERTIFICATE_FAILURE [ECUC_Dcm_01209]

Parent Container DcmSecurityEventRefs
Description The tester tried an authentication with an invalid certificate.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

681 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DIAG_SEV_CLEAR_DTC_SUCCESSFUL [ECUC_Dcm_01198]

Parent Container DcmSecurityEventRefs
Description DTC information has been cleared by SID 0x14 ClearDTCInformation

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DIAG_SEV_COMMUNICATION_CONTROL_SWITCHED_OFF
[ECUC_Dcm_01191]
Parent Container DcmSecurityEventRefs
Description ECU communication was switched off with service
CommunicationControl.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

682 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DIAG_SEV_DTC_SETTING_SWITCHED_OFF [ECUC_Dcm_01202]

Parent Container DcmSecurityEventRefs
Description DTC setting switched off with service 0x85 (ControlDTCSetting).

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DIAG_SEV_ECU_RESET [ECUC_Dcm_01199]

Parent Container DcmSecurityEventRefs
Description ECU had been reset by SID 0x11 ResetECU.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

683 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DIAG_SEV_ECU_UNLOCK_SUCCESSFUL [ECUC_Dcm_01196]

Parent Container DcmSecurityEventRefs
Description Successfully unlocked the ECU (via Security Access $27), per Level

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DIAG_SEV_INCORRECT_MESSAGE_LENGTH_OR_FORMAT
[ECUC_Dcm_01194]
Parent Container DcmSecurityEventRefs
Description Received request message does not match the specified length or the
format of the parameters is different from the specified ones for that
service. NRC 0x13 (incorrectMessageLengthOrInvalidFormat) was
returned.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

684 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DIAG_SEV_NUMBER_OF_FAILED_AUTHENTICATION_ATTEMPTS
_EXCEEDED [ECUC_Dcm_01208]
Parent Container DcmSecurityEventRefs
Description Number of failed authentication attempts - OEM specific

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DIAG_SEV_REQUEST_DOWNLOAD [ECUC_Dcm_01201]

Parent Container DcmSecurityEventRefs
Description A diagnostic data download sequence was requested with SID 0x34.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

685 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DIAG_SEV_REQUEST_OUT_OF_RANGE [ECUC_Dcm_01203]

Parent Container DcmSecurityEventRefs
Description A diagnostic request with a parameter that is out of range of the
allowed bounds was received. A NRC 0x31 (requestOutOfRange) was
returned.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DIAG_SEV_REQUEST_SEQUENCE_ERROR [ECUC_Dcm_01195]

Parent Container DcmSecurityEventRefs
Description A diagnostic service was received in the wrong sequence order. NRC
0x24 (requestSequenceError) was returned.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

686 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DIAG_SEV_REQUESTED_ACTIONS_REQUIRES_AUTHENTICATIO
N [ECUC_Dcm_01204]
Parent Container DcmSecurityEventRefs
Description A diagnostic request was received while the required authentication to
execute this service is not given. NRC 0x34 (authenticationRequired)
was returned.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DIAG_SEV_SECURITY_ACCESS_DENIED [ECUC_Dcm_01190]

Parent Container DcmSecurityEventRefs
Description Tester has sent an diagnostic request without meeting the servers
security level requirements for that service. NRC 0x33
(securityAccessDenied) was returned.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

687 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DIAG_SEV_SECURITY_ACCESS_INVALID_KEY
[ECUC_Dcm_01206]
Parent Container DcmSecurityEventRefs
Description Security Access failed because the tester has sent an invalid key to the
server. An NRC 0x35 (invalidKey) was returned.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DIAG_SEV_SECURITY_ACCESS_NUMBER_OF_ATTEMPTS_EXCE
EDED [ECUC_Dcm_01205]
Parent Container DcmSecurityEventRefs
Description Security Access failed and the number of invalid attempts has been
exceeded. NRC 0x36 (exceedNumberOfAttempts) was returned.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

688 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DIAG_SEV_SECURITY_ACCESS_REQUIRED_TIME_DELAY_NOT_
EXPIRED [ECUC_Dcm_01207]
Parent Container DcmSecurityEventRefs
Description A further attempt to unlock the ECU was taken before the delay time
had expired. NRC 0x37 (requiredTimeDelayNotExpired) was sent.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DIAG_SEV_SERVICE_NOT_SUPPORTED [ECUC_Dcm_01192]

Parent Container DcmSecurityEventRefs
Description A diagnostic service was requested that is not supported or not
supported in the active session. NRC 0x11 (serviceNotSupported) or
NRC 0x7F (serviceNotSupportedInActiveSession) was returned.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

689 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DIAG_SEV_SUBFUNCTION_NOT_SUPPORTED
[ECUC_Dcm_01193]
Parent Container DcmSecurityEventRefs
Description A subfunction of a diagnostic service was requested that is not
supported for the requested service.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name DIAG_SEV_WRITE_DATA [ECUC_Dcm_01200]

Parent Container DcmSecurityEventRefs
Description Diagnostic data identifier has been written by SID 0x2E.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

690 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Name DIAG_SEV_WRITE_INV_DATA [ECUC_Dcm_01189]

Parent Container DcmSecurityEventRefs
Description Tester writes invalid data with service WriteDataByIdentifier.

Tags:
atp.Status=draft
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

691 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

No Included Containers
DcmGeneral:
EcucParamConfContainerDef +parameter DcmEnableSecurityEventReporting:
EcucBooleanParamDef
lowerMultiplicity = 1
upperMultiplicity = 1 defaultValue = false

+subContainer

DcmSecurityEventRefs: DIAG_SEV_WRITE_INV_DATA: EcucReferenceDef IdsMEvent:

EcucParamConfContainerDef +destination EcucParamConfContainerDef
+reference lowerMultiplicity = 0
lowerMultiplicity = 0 upperMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1 requiresSymbolicNameValue = true upperMultiplicity = 65535

DIAG_SEV_SECURITY_ACCESS_DENIED: EcucReferenceDef
+reference lowerMultiplicity = 0 +destination
upperMultiplicity = 1
requiresSymbolicNameValue = true

DIAG_SEV_COMMUNICATION_CONTROL_SWITCHED_OFF:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

DIAG_SEV_SERVICE_NOT_SUPPORTED: EcucReferenceDef
+reference +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

DIAG_SEV_SUBFUNCTION_NOT_SUPPORTED:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

DIAG_SEV_INCORRECT_MESSAGE_LENGTH_OR_FORMAT:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

DIAG_SEV_REQUEST_SEQUENCE_ERROR:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

(from IdsM)

Figure 10.60: DcmSecurityEventRefs1 configuration overview

692 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmGeneral:
EcucParamConfContainerDef +parameter DcmEnableSecurityEventReporting:
EcucBooleanParamDef
lowerMultiplicity = 1
upperMultiplicity = 1 defaultValue = false

+subContainer

DcmSecurityEventRefs: DIAG_SEV_REQUEST_OUT_OF_RANGE: EcucReferenceDef IdsMEvent:

EcucParamConfContainerDef EcucParamConfContainerDef
+reference lowerMultiplicity = 0 +destination
lowerMultiplicity = 0 upperMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1 requiresSymbolicNameValue = true upperMultiplicity = 65535

DIAG_SEV_REQUESTED_ACTIONS_REQUIRES_AUTHENTICATION:
EcucReferenceDef +destination
+reference
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

DIAG_SEV_SECURITY_ACCESS_NUMBER_OF_ATTEMPTS_EXCEEDED:
EcucReferenceDef +destination
+reference
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

DIAG_SEV_SECURITY_ACCESS_INVALID_KEY: EcucReferenceDef
+reference +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

DIAG_SEV_SECURITY_ACCESS_REQUIRED_TIME_DELAY_NOT_EXPIRED:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

DIAG_SEV_NUMBER_OF_FAILED_AUTHENTICATION_ATTEMPTS_EXCEEDED:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

DIAG_SEV_CERTIFICATE_FAILURE: EcucReferenceDef
+reference +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

(from IdsM)

Figure 10.61: DcmSecurityEventRefs2 configuration overview

693 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

DcmGeneral:
EcucParamConfContainerDef +parameter DcmEnableSecurityEventReporting:
EcucBooleanParamDef
lowerMultiplicity = 1
upperMultiplicity = 1 defaultValue = false

+subContainer

DcmSecurityEventRefs: DIAG_SEV_ECU_UNLOCK_SUCCESSFUL: IdsMEvent:

EcucParamConfContainerDef EcucReferenceDef +destination EcucParamConfContainerDef
+reference
lowerMultiplicity = 0 lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = 1 upperMultiplicity = 65535
requiresSymbolicNameValue = true

DIAG_SEV_AUTHENTICATION_SUCCESSFUL:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

DIAG_SEV_CLEAR_DTC_SUCCESSFUL:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

DIAG_SEV_ECU_RESET: EcucReferenceDef
+reference lowerMultiplicity = 0 +destination
upperMultiplicity = 1
requiresSymbolicNameValue = true

DIAG_SEV_WRITE_DATA: EcucReferenceDef
+reference +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

DIAG_SEV_REQUEST_DOWNLOAD:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

DIAG_SEV_DTC_SETTING_SWITCHED_OFF:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

(from IdsM)

Figure 10.62: DcmSecurityEventRefs3 configuration overview

694 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

10.3 Protocol Configuration Example

Figure 10.63: Examples of protocol configuration with focus on buffer / DcmPduId set-
tings

Above example shows protocol configuration at the use cases examples OBD and UDS
(used for customer enhanced diagnosis). It is assumed that for UDS communication,
there are functional and physical requests. There will be separate DcmPduRxIds for
functional and physical reception.

695 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

Concerning buffer configuration it is proposed to use a separate buffer for the func-
tional requests. This in correspondence to support the keep alive logic with functional
addressed TesterPresent commands.
It is also proposed to use a separate receive buffer for the OBD commands. This in
reference to support the protocol switch functionality.
It is allowed to share for both protocols the transmit buffer. Please note: The DcmDsl-
ProtocolRx has two possible configurations:
• functional
• physical
The physical shall have a 1:1 (or 1:0) dependency to the DcmDslMain-
Connection. (which means: DcmDslProtocolRxPduRef in combination
DCM_PROTOCOL_RX_ADDR_TYP = physical can exist only once per "Mod-
ule") The functional shall have a 1:n dependency to the DcmDslMain-
Connection. (which means: DcmDslProtocolRxPduRef in combination
DCM_PROTOCOL_RX_ADDR_TYP = functional can exist several times per "Module")
The DcmDslProtocolTx shall exist only once per "Module"

10.4 Published Information

For details refer to the chapter 10.3 "Published Information" in SWS_BSWGeneral [7].

A Not applicable requirements

[SWS_Dcm_NA_00999] dThese requirements are not applicable to this specifica-
tion.c(SRS_BSW_00005, SRS_BSW_00006, SRS_BSW_00007, SRS_BSW_00009,

696 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R20-11

SRS_BSW_00010, SRS_BSW_00158, SRS_BSW_00159, SRS_BSW_00160, SRS_-

BSW_00161, SRS_BSW_00162, SRS_BSW_00164, SRS_BSW_00167, SRS_-
BSW_00168, SRS_BSW_00170, SRS_BSW_00171, SRS_BSW_00172, SRS_-
BSW_00300, SRS_BSW_00301, SRS_BSW_00304, SRS_BSW_00305, SRS_-
BSW_00306, SRS_BSW_00307, SRS_BSW_00308, SRS_BSW_00309, SRS_-
BSW_00310, SRS_BSW_00312, SRS_BSW_00314, SRS_BSW_00318, SRS_-
BSW_00321, SRS_BSW_00323, SRS_BSW_00325, SRS_BSW_00327, SRS_-
BSW_00328, SRS_BSW_00330, SRS_BSW_00331, SRS_BSW_00333, SRS_-
BSW_00334, SRS_BSW_00335, SRS_BSW_00336, SRS_BSW_00339, SRS_-
BSW_00341, SRS_BSW_00342, SRS_BSW_00343, SRS_BSW_00344, SRS_-
BSW_00345, SRS_BSW_00346, SRS_BSW_00347, SRS_BSW_00350, SRS_-
BSW_00351, SRS_BSW_00353, SRS_BSW_00357, SRS_BSW_00358, SRS_-
BSW_00359, SRS_BSW_00360, SRS_BSW_00361, SRS_BSW_00371, SRS_-
BSW_00374, SRS_BSW_00375, SRS_BSW_00377, SRS_BSW_00378, SRS_-
BSW_00379, SRS_BSW_00380, SRS_BSW_00383, SRS_BSW_00384, SRS_-
BSW_00385, SRS_BSW_00386, SRS_BSW_00388, SRS_BSW_00389, SRS_-
BSW_00390, SRS_BSW_00392, SRS_BSW_00393, SRS_BSW_00394, SRS_-
BSW_00395, SRS_BSW_00396, SRS_BSW_00397, SRS_BSW_00398, SRS_-
BSW_00399, SRS_BSW_00400, SRS_BSW_00401, SRS_BSW_00402, SRS_-
BSW_00403, SRS_BSW_00404, SRS_BSW_00405, SRS_BSW_00406, SRS_-
BSW_00408, SRS_BSW_00409, SRS_BSW_00410, SRS_BSW_00411, SRS_-
BSW_00413, SRS_BSW_00414, SRS_BSW_00415, SRS_BSW_00416, SRS_-
BSW_00417, SRS_BSW_00419, SRS_BSW_00422, SRS_BSW_00423, SRS_-
BSW_00425, SRS_BSW_00426, SRS_BSW_00427, SRS_BSW_00428, SRS_-
BSW_00429, SRS_BSW_00432, SRS_BSW_00433, SRS_BSW_00437, SRS_-
BSW_00439, SRS_BSW_00440, SRS_BSW_00441, SRS_BSW_00447, SRS_-
BSW_00448, SRS_BSW_00449, SRS_BSW_00450, SRS_BSW_00451, SRS_-
BSW_00452, SRS_BSW_00453, SRS_BSW_00454, SRS_BSW_00456, SRS_-
BSW_00457, SRS_BSW_00458, SRS_BSW_00459, SRS_BSW_00460, SRS_-
BSW_00461, SRS_BSW_00462, SRS_BSW_00463, SRS_BSW_00464, SRS_-
BSW_00465, SRS_BSW_00466, SRS_BSW_00467, SRS_BSW_00469, SRS_-
BSW_00470, SRS_BSW_00471, SRS_BSW_00472, SRS_BSW_00473, SRS_-
BSW_00477, SRS_BSW_00478, SRS_BSW_00479, SRS_BSW_00480, SRS_-
BSW_00481, RS_Diag_04002, RS_Diag_04007, RS_Diag_04019, RS_Diag_04024,
RS_Diag_04031, RS_Diag_04032, RS_Diag_04057, RS_Diag_04059, RS_Diag_-
04063, RS_Diag_04064, RS_Diag_04068, RS_Diag_04071, RS_Diag_04077, RS_-
Diag_04085, RS_Diag_04086, RS_Diag_04087, RS_Diag_04089, RS_Diag_04090,
RS_Diag_04091, RS_Diag_04093, RS_Diag_04097, RS_Diag_04100, RS_Diag_-
04101, RS_Diag_04105, RS_Diag_04107, RS_Diag_04109, RS_Diag_04110, RS_-
Diag_04111, RS_Diag_04112, RS_Diag_04113, RS_Diag_04117, RS_Diag_04118,
RS_Diag_04119, RS_Diag_04120, RS_Diag_04121, RS_Diag_04123, RS_Diag_-
04124, RS_Diag_04125, RS_Diag_04126, RS_Diag_04127, RS_Diag_04129, RS_-
Diag_04131, RS_Diag_04133, RS_Diag_04135, RS_Diag_04136, RS_Diag_04137,
RS_Diag_04139, RS_Diag_04140, RS_Diag_04143, RS_Diag_04144, RS_Diag_-
04145, RS_Diag_04146, RS_Diag_04148, RS_Diag_04150, RS_Diag_04151)

697 of 697 Document ID 18: AUTOSAR_SWS_DiagnosticCommunicationManager