SNIP_CLASSIC_LINIF_SECTION_8_2_16_LinTp_Transmit

8.2.16 LinTp_Transmit [SWS_LinIf_00351] Definition of API function LinTp_Transmit ⌈ Service Name LinTp_Transmit Syntax Std_ReturnType LinTp_Transmit ( PduIdType TxPduId, const PduInfoType* PduInfoPtr ) Service ID [hex] 0x53 Sync/Async Synchronous Reentrancy Reentrant for different PduIds. Non reentrant for the same PduId. TxPduId Identifier of the PDU to be transmitted Parameters (in) PduInfoPtr Length of and pointer to the PDU data and pointer to MetaData. Parameters (inout) None ▽ △ Parameters (out) None Return value Std_ReturnType E_OK: Transmit request has been accepted. E_NOT_OK: Transmit request has not been accepted. Description Requests transmission of a PDU. Available via LinIf.h ⌋ [SWS_LinIf_00326] ⌈The function LinTp_Transmit shall prepare a LIN TP message for transmission.⌋ The LIN Interface’s environment shall call the function LinIf_Init for initializing the referenced channel before using the function LinTp_Transmit. [SWS_LinIf_00413] ⌈The function LinTp_Transmit shall set the sub-state of the referenced channel to LINTP_CHANNEL_BUSY.⌋ [SWS_LinIf_00422] ⌈The function LinTp_Transmit shall convert the N-SDU Id (given by the parameter TxPduId) to a specific channel and a destination NAD for the slave. This requirement is only applicable to LIN master nodes.⌋ [SWS_LinIf_00584] ⌈The function LinTp_Transmit shall accept a functional transmission request also when a TP message is currently ongoing on the selected channel. This requirement is only applicable to LIN master nodes.⌋ [SWS_LinIf_00616] ⌈If the transmission for a further physical request is triggered while transmission of a previously triggered physical request is ongoing, the LIN Interface shall accept the new physical request and drop the old physical request.⌋ Note: According to the ISO 17987 specifications, the NAD 0x7E shall be used for a functional transmission request. [SWS_LinIf_00586] ⌈The LIN Interface shall use the NAD 0x7E for transmission of functional requests by LIN master nodes.⌋ [SWS_LinIf_00702] Upstream requirements: SRS_Lin_01564 ⌈When LinTp_Transmit was successful (returned E_OK), the LIN Interface shall call PduR_LinTpTxConfirmation after successful completion or failure (e.g., since some other schedule table change is currently going on) of required schedule table switch (see [SWS_LinIf_00646], [SWS_LinIf_00642], [SWS_LinIf_00643], [SWS_LinIf_00707]), with a negative or positive result. When LinTp_Transmit was not successful, PduR_LinTpTxConfirmation shall not be called.⌋ [SWS_LinIf_00878] Upstream requirements: SRS_Lin_01564 ⌈The function LinTp_Transmit shall return E_NOT_OK when the corresponding LinIf_ScheduleRequest call (called from BswM_LinTp_RequestMode resulting from the LinTp_Transmit call, see [SWS_LinIf_00646] and [SWS_LinIf_00641]) returned E_NOT_OK for the Schedule Request.⌋ [SWS_LinIf_00574] ⌈If development error detection is enabled and the parameter PduInfoPtr has an invalid value, the function LinTp_Transmit shall raise the development error code LINIF_E_PARAM_POINTER.⌋ [SWS_LinIf_00576] ⌈If development error detection is enabled and the parameter TxPduId has an invalid value, the function LinTp_Transmit shall raise the development error code LINIF_E_PARAMETER.⌋ [SWS_LinIf_00682] ⌈The function LinTp_Transmit shall be pre-compile time configurable On/Off by the configuration parameter LinIfTpSupported.⌋ Caveats: The LIN Interface has to be initialized with a call of LinIf_Init and LinTp_Init before this API service may be called, see [SRS_BSW_00487].