SNIP_CLASSIC_STD_SECTION_7_2_4_5_2_Rte_Rips_Write

7.2.4.5.2 Rte_Rips_Write [SWS_Rte_89021] Definition of API function Rte_Rips_<PlugIn>_Write_[<Swc BswI>][Partition][_<ExE>]_<CGI> Upstream requirements: SRS_Rte_00300, SRS_Rte_00301, SRS_Rte_00306, SRS_BSW_00310 ⌈ Service Name Rte_Rips_<PlugIn>_Write_[<SwcBswI>][Partition][_<ExE>]_<CGI> Syntax Std_ReturnType Rte_Rips_<PlugIn>_Write_[<SwcBswI>][Partition][_<Ex E>]_<CGI> ( IN <data>, [Std_TransformerError transformerError] ) Service ID [hex] 0xEB Sync/Async Synchronous Reentrancy Reentrant Parameters (in) <data> The IN parameter <data> pass the received data. Parameters (inout) None Parameters (out) transformerError The OUT parameter transformerError contains the transformer error which occurred during execution of the transformer chain. Return value Std_ReturnType The return value is used to indicate communication errors. Description Rte_Rips_Write Performs an "explicit" write on a sender-receiver communication data element. Available via Rte_Rips_<PlugIn>_<SwcBswI>.h ⌋ Please note that the name part [_<ExE>] in the Rte_Rips_Write Service only exists in case of protection of explicitInterRunnableVariables. [SWS_Rte_70056] Upstream requirements: SRS_Rte_00306, SRS_Rte_00300, SRS_Rte_00303 ⌈The associated Local Software Cluster Communication Plug-In shall provide the Rte_Rips_Write Service for each VariableDataPrototype instance in an AbstractProvidedPortPrototype for which an VariableAccess of a RunnableEntity in the role dataSendPoint exists and for each VariableAccess in role writtenLocalVariable to an explicitInterRunnableVariable if • for the related Data Communication Graph the Local Software Cluster Communication Plug-In support is enabled AND – for the associated Local Software Cluster Communication Plug-In the RteRipsGlobalCopyInstantiationPolicy is set to RTE_RIPS_INSTANTIATION_BY_PLUGIN. OR – a data transformation is configured according [SWS_Rte_08794] or [SWS_Rte_08105]. ⌋ [SWS_Rte_70057] Upstream requirements: SRS_Rte_00306, SRS_Rte_00300, SRS_Rte_00303 ⌈The associated Local Software Cluster Communication Plug-In shall provide the Rte_Rips_Write Service for each BswVariableAccess of a BswModuleEntity in the role dataSendPoint if • for the related Data Communication Graph the Local Software Cluster Communication Plug-In support is enabled AND • for the associated Local Software Cluster Communication Plug- -In the RteRipsGlobalCopyInstantiationPolicy is set to RTE_RIPS_ INSTANTIATION_BY_PLUGIN. ⌋ [SWS_Rte_70131] Upstream requirements: SRS_Rte_00306, SRS_Rte_00300, SRS_Rte_00303 ⌈The associated Cross Software Cluster Communication Plug-In shall provide the Rte_Rips_Write Service for each VariableDataPrototype instance in an AbstractProvidedPortPrototype for which an VariableAccess of a RunnableEntity in the role dataSendPoint exists if • for the related Data Communication Graph the Cross Software Cluster Communication Plug-In support is enabled AND • for the dataElement “event” semantics (swImplPolicy = queued) applies. ⌋ [SWS_Rte_70132] Upstream requirements: SRS_Rte_00306, SRS_Rte_00300, SRS_Rte_00303 ⌈In case of the existence condition described in [SWS_Rte_70056], [SWS_Rte_70057], [SWS_Rte_70131] the optional name part [<SwcBswI>] exists for the related Rte_Rips_Write Services.⌋ [SWS_Rte_70133] Upstream requirements: SRS_Rte_00306, SRS_Rte_00300, SRS_Rte_00303 ⌈The associated Cross Software Cluster Communication Plug-In shall provide the Rte_Rips_Write Service once for each partition which has a software component mapped to it where the software component has a VariableDataPrototype instance in an AbstractProvidedPortPrototype for which an VariableAccess of a RunnableEntity in the role • dataSendPoint or • dataWriteAccess exists AND • for the related Data Communication Graph the Cross Software Cluster Communication Plug-In support is enabled AND • for the dataElement “last-is-best” semantics (swImplPolicy = standard) applies. ⌋ [SWS_Rte_70134] Upstream requirements: SRS_Rte_00306, SRS_Rte_00300, SRS_Rte_00303 ⌈In case of the existence condition described in [SWS_Rte_70133] the optional name part [Partition] exists for the related Rte_Rips_Write Services.⌋ [SWS_Rte_70058] Upstream requirements: SRS_Rte_00306, SRS_Rte_00300 ⌈The optional OUT parameter transformerError of the Rte_Rips_Write service shall be generated according to [SWS_Rte_08574].⌋ The return value is used to indicate errors detected by the RTE Implementation Plug-In during execution of the Rte_Rips_Write service call or errors detected by the communication system. • [SWS_Rte_70059] Upstream requirements: SRS_Rte_00306, SRS_Rte_00300, SRS_Rte_00094 ⌈RTE_E_OK – data written successfully.⌋ • [SWS_Rte_70060] Upstream requirements: SRS_Rte_00306, SRS_Rte_00300, SRS_Rte_00094, SRS_Rte_ 00091 ⌈RTE_E_HARD_TRANSFORMER_ERROR – The return value of one transformer in the transformer chain represented a hard transformer error.⌋ • [SWS_Rte_70061] Upstream requirements: SRS_Rte_00306, SRS_Rte_00300, SRS_Rte_00094, SRS_Rte_ 00091 ⌈RTE_E_SOFT_TRANSFORMER_ERROR – The return value of at least one transformer in the transformer chain was a soft error and no hard error occurred in the transformer chain.⌋ • [SWS_Rte_70102] Upstream requirements: SRS_Rte_00306, SRS_Rte_00300, SRS_Rte_00143 ⌈RTE_E_LIMIT – an ‘event’ has been discarded due to a full queue by one of the ECU local receivers (intra ECU communication only).⌋ [SWS_Rte_70138] Upstream requirements: SRS_Rte_00028, SRS_Rte_00306, SRS_Rte_00300 ⌈In case of multiple faults during a call of Rte_Rips_Write the resulting return value shall be derived according to the following priority rules (highest priority first): 1. RTE_E_LIMIT 2. RTE_E_HARD_TRANSFORMER_ERROR 3. RTE_E_SOFT_TRANSFORMER_ERROR ⌋ [SWS_Rte_80066] Upstream requirements: SRS_Rte_00306, SRS_Rte_00300, SRS_Rte_00303 ⌈The RTE shall call Rte_Rips_Write at the position and instead of the RTE’s regular write access to the data, if • for the related Data Communication Graph the Local Software Cluster Communication Plug-In support is enabled AND