0
1

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?

More than 1 year has passed since last update.

Specification of Communication Stack Types, No.50, AUTOSAR R21-11(259) CP

Last updated at Posted at 2022-05-29

Specification of Communication Stack Types, No.50, 2021-11

AUTOSAR R21-11記事一覧はこちら。

AUTOSAR 21-11,160文書読んだ。2022年5月中に全部読み。

AUTOSAR 21-11, 62文書読んだ。2022年5月中に半分到達予定。

AUTOSAR R21-11(0) 仕様ダウンロード一覧。単語帳。参考文献資料作成

用語(terms)

Term Description
API Application Programming Interface
DCM Diagnostic Communication Manager
I-PDU Interaction Layer PDU. In AUTOSAR the Interaction Layer is equivalent to the Communication Services Layer.
L-PDU Data Link Layer PDU. In AUTOSAR the Data Link Layer is equivalent to the Communication Hardware Abstraction and Microcontroller Abstraction Layer.
N-PDU Network Layer PDU. In AUTOSAR the Network Layer is equivalent to the Transport Protocol.
OSEK/VDX In May 1993 OSEK has been founded as a joint project in the German automotive industry aiming at an industry standard for an open-ended architecture for distributed control units in vehicles. OSEK is an abbreviation for the German term "Offene Systeme und deren Schnittstellen für die Elektronik im Kraftfahrzeug" (English: Open Systems and the Corresponding Interfaces for Automotive Electronics). Initial project partners were BMW, Bosch, DaimlerChrysler, Opel, Siemens, VW and the IIIT of the University of Karlsruhe as co-ordinator. The French car manufacturers PSA and Renault joined OSEK in 1994 introducing their VDX-approach (Vehicle Distributed eXecutive) which is a similar project within the French automotive industry. At the first workshop on October 1995 the OSEK/VDX group presented the results of the harmonised specification between OSEK and VDX. After the 2nd international OSEK/VDX Workshop in October 1997 the 2nd versions of the specifications were published.
PDU Protocol Data Unit
SDU Service Data Unit - Payload of PDU
TP Transport Protocol
Com Communication
EcuC ECU Configuration
e.g. [lat.] exempli gratia = [eng.] for example
i.e. [lat.] it est = [eng.] that is

英日

日本語は仮訳

T.B.D.

参考(reference)

[1] [GeneralSRS] General Requirements on Basic Software Modules
AUTOSAR_SRS_BSWGeneral.pdf
[2] [SRSSPAL] General Requirements on
SPAL AUTOSAR_SRS_SPALGeneral.pdf
[3] [StdTypes] Specification of Standard Types
AUTOSAR_SWS_Std_Types.pdf
[4] [PltfTypes] Specification of Platform Types
AUTOSAR_SWS_Platform_Types.pdf
[5] [CompTypes] Specification of Compiler Abstraction
AUTOSAR_SWS_CompilerAbstraction.pdf
[6] [CANTP] Specification of CAN Transport Layer
AUTOSAR_SWS_CANTransportLayer.pdf
[7] [FlexRayTP] Specification of FlexRay Transport Layer
AUTOSAR_SWS_FlexRayTransportLayer.pdf
[8] [CANTRCV] Specification of CAN Transceiver Driver
AUTOSAR_SWS_CANTransceiverDriver.pdf
[9] [FRTRCV] Specification of FlexRay Transceiver Driver
AUTOSAR_SWS_FlexRayTransceiverDriver.pdf
[10] [BSMDT]Basic Software Module Description Template,
AUTOSAR_TPS_BSWModuleDescriptionTemplate.pdf
[11] [BSWModule]List of Basic Software Modules
AUTOSAR_TR_BSWModuleList
[12] [BSWGeneral]General Specification of Basic Software Modules
AUTOSAR_SWS_BSWGeneral.pdf
[CProgLang] ISO/IEC 9899:1990 Programming Language – C
[ISONM] ISO/IEC 15765-2; 2003 Diagnostics on Controller Area Networks (CAN) –
Network layer services

0
1
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
0
1

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?