SNIP_CLASSIC_COMM_SECTION_9_4_Communication_request

9.4 Communication request Figure 9.4 shows the possibilities to start COMM_FULL_COMMUNICATION on CAN. It can be either initiated if a user requests COMM_FULL_COMMUNICATION request or DCM indicates ComM_DCM_ActiveDiagnostic (see [SWS_ComM_00873]). The behaviour is equal for LIN, FlexRay and Ethernet just with different API names. «module» EcuM «module» Dcm «module» Rte «module» ComM «module» Nm «module» CanSM alt Active start up [User request] [Active diagnostic]
              alt NM Variant [Full] [Passive] [None/Light] COMM_NO_COM_NO_PENDING_REQUEST COMM_NO_COM_REQUEST_PENDING COMM_FULL_COM_NETWORK_REQUESTED Wait for Communication Allowed = true Start timer ComMTMinFullComModeDuration ComM_Nm_NetworkMode(...) ComM_Nm_NetworkMode(Channel) ComM_<Bus>SM_ModeIndication(Channel, ComMode: =COMM_FULL_COMMUNICATION) NM_NetworkRequest(...)=E_OK Nm_NetworkRequest(NetworkHandle) CanSM_RequestComMode(network, mode: =COMM_FULL_COMMUNICATION) ComM_Nm_NetworkMode(Channel) CanSM_RequestComMode(...)=E_OK ComM_DCM_ActiveDiagnostic (NetworkHandleType) ComM_RequestComMode(Std_ReturnType, ComM_UserHandleType, ComM_ModeType) Figure 9.4: Request Communication