DEENESPTFRRUARHIKOZHNL
CLASSIC Modul: dcm Rolle: heuristic Konfidenz: 80%

SNIP_CLASSIC_DCM_SECTION_7_4_2_9_Service_0x28_CommunicationControl

Quelle: SWS_DiagnosticCommunicationManager.pdf (Seite 147) • Ziel-Anforderung: SWS_Dcm_91025

Wortlaut

7.4.2.9 Service 0x28 - CommunicationControl [SWS_Dcm_00511] ⌈The Dcm module shall implement the CommunicationControl (service 0x28) of the Unified Diagnostic Services.⌋ [SWS_Dcm_00512] ⌈On invocation of the sent confirmation function of the UDS Service CommunicationControl (0x28) from DSD with the subnet parameter of the request equal to 0x00, the Dcm shall do for each NetworkHandle (see DcmDspAllComMChannelRef) which is configured in DcmDspComControlAllChannel: 1. trigger the mode switch Dcm_CommunicationControl_<Network> ModeDeclarationGroupPrototype to the mode corresponding 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). ⌋ [SWS_Dcm_00785] ⌈On invocation of the sent confirmation function of the UDS Service CommunicationControl (0x28) from DSD with the subnet parameter of the request 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> ModeDeclarationGroupPrototype 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) ⌋ Manager [SWS_Dcm_00786] ⌈On invocation of the sent confirmation function of the UDS Service 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 corresponding NetworkHandle (see DcmDspSpecificComMChannelRef) of the received subnet parameter (see DcmDspSubnetNumber): 1. trigger the mode switch Dcm_CommunicationControl_<Network> ModeDeclarationGroupPrototype to the mode corresponding the communicationType and controlType parameter from the CommunicationControl request. 2. call the Api BswM_Dcm_CommunicationMode_CurrentState the parameters NetworkHandleType and with Dcm_CommunicationModeType corresponding the communicationType and controlType parameter from the CommunicationControl request (see Dcm_CommunicationModeType definition) ⌋ For some use-cases the Dcm may re-enable the CommunicationControl due to external changed mode conditions: [SWS_Dcm_00753] ⌈In 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> ModeDeclarationGroupPrototype toDCM_ENABLE_RX_TX_NORM_NM 2. call BswM_Dcm_CommunicationMode_CurrentState with the parameters NetworkHandleType set to the corresponding NetworkHandle of the network and RequestedCommunicationMode set to DCM_ENABLE_RX_TX_NORM_NM ⌋ [SWS_Dcm_00860] ⌈For 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 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> ModeDeclarationGroupPrototype to DCM_ENABLE_RX_TX_NORM_NM 2. call BswM_Dcm_CommunicationMode_CurrentState with the parameters NetworkHandleType set to the corresponding NetworkHandle of the network and RequestedCommunicationMode set to DCM_ENABLE_RX_TX_NORM_NM ⌋ Manager Note: the NetworkHandles to be considered are all ComM channels which are referenced from either DcmDspSpecificComMChannelRef, DcmDspAllComMChannelRef or DcmDspComControlSubNodeComMChannelRef. [SWS_Dcm_01077] ⌈If a CommunicationControl Request with the sub-function "enableRxAndDisableTxWithEnhancedAddressInformation" 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> ModeDeclarationGroupPrototype to the mode corresponding 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). 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. ⌋ [SWS_Dcm_01078] ⌈The 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.⌋ [SWS_Dcm_01079] ⌈If a CommunicationControl Request with the sub-function "enableRxAndTxWithEnhancedAddressInformation" 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> ModeDeclarationGroupPrototype to the mode corresponding 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). Manager 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. ⌋ [SWS_Dcm_01080] ⌈The Dcm shall trigger a negative response with NRC 0x31 (RequestOutOfRange), if a CommunicationControl Request with the sub-function "enableRxAndTxWithEnhancedAddressInformation" and a "nodeIdentification-Number" which is not listed as DcmDspComControlSubNodeId is received.⌋ [SWS_Dcm_01081] ⌈If DcmDspComControlSubNodeUsed is set to FALSE the sub-system (DcmDspComControlSubNode) is not available in this configuration.⌋ [SWS_Dcm_01082] ⌈If DcmDspComControlSubNodeUsed is set to TRUE the sub-system (DcmDspComControlSubNode) is available in this configuration.⌋ 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 CommunicationType) are not directly supported by the Dcm. Supplier/manufacturer notifications can be used.

Versionen & Provenienz · Zugeordnete Anforderungen

Diese Angaben zeigt der Versions-Explorer.

Begründung & Zuweisungs-Evidenz

Defines modes switched during communication control.

Dokumenten-Herkunft & Rückverfolgbarkeit

Spezifikations-Dokument SWS_DiagnosticCommunicationManager.pdf
Dokumentseite Seite 147
Ziel-Modul dcm (classic)
Ziel-Anforderung SWS_Dcm_91025
Semantische Rolle heuristic
Automatisierungs-Konfidenz 0.80