Log and Trace Protocol Specification, AUTOSAR 787, R23-11, FO

AUTOSARが、2022年の版、R22-11を公開しました。
https://www.autosar.org/fileadmin/standards/R23-11/FO/AUTOSAR_FO_PRS_LogAndTraceProtocol.pdf

R22-11
https://www.autosar.org/fileadmin/standards/R22-11/FO/AUTOSAR_PRS_LogAndTraceProtocol.pdf

R21-11
https://www.autosar.org/fileadmin/standards/R21-11/FO/AUTOSAR_PRS_LogAndTraceProtocol.pdf

R20-11
https://www.autosar.org/fileadmin/standards/R20-11/FO/AUTOSAR_PRS_LogAndTraceProtocol.pdf

R19-11
https://www.autosar.org/fileadmin/standards/R19-11/FO/AUTOSAR_PRS_LogAndTraceProtocol.pdf

文書は検索してダウンロードできます。
https://www.autosar.org/



<この項は書きかけです。順次追記します。>
This article is not completed. I will add some words in order.

# Release Overviews

AUTOSARには現在3つの分類があります。Foundation, CAN OSEK/VDXのClassic Platform, Ethernet/TCP/IP POSIXのAdaptive Platform.

Foundation Release Overview, AUTOSAR 781, R23-11, FO
https://qiita.com/kaizen_nagoya/items/f249bdb8c313d8bff883

Classic Platform Release Overview, AUTOSAR No.0 ,R23-11, CP
https://qiita.com/kaizen_nagoya/items/9d22c8722cbc0f42b137

Adaptive Platform Release Overview, AUTOSAR 782, R23-11, AP
https://qiita.com/kaizen_nagoya/items/13a104606a34fe24fcf7

# Qiita 記事一覧


Autosar Foundation R23-11 一覧
https://qiita.com/kaizen_nagoya/items/c30674cb2dac2fcbbd04

AUTOSAR Adaptive Platform R23-11一覧
https://qiita.com/kaizen_nagoya/items/1dece8799a730367b0dc

Autosar Classic Platform R23-11 一覧
https://qiita.com/kaizen_nagoya/items/f770f6c2906e1dcbf180


# 文書変更(Document Change) 

>• Offset corrections in Storage Header 
• Segmentation-Information refinement 
• LogLevel type "Information" updatedpport of long Appl-IDs and Context- IDs added

# 用語(term)

|short name/term| description|
|:--|:--|
|APID|Application ID|
|CNTI|Content information|
|CTID|Context ID
|Dlt|Diagnostic Log and Trace
|HTYP|Header Type
|LEN|Overall Message Length
|MCNT|Message Counter
|MSID|Message ID
|MSIN|Message Info
|MSTP|Message Type
|MTIN|Message Type Info
|NOAR|Number of Arguments
|TMSP|Timestamp
|VERB|Verbose
|VERS|Version Number
|WACID|With App- and Context ID
|WEID|With ECU ID
|WPVL|With Privacy Level
|WSFLN|With Source File Name and Line Number
|WSID|With Session ID
|WTGS|With Tags
|Log and trace message|A log and trace message contains all data and options to describe a log and trace event in a software. The log and trace message consists of a header and payload.
|Dlt User |A Dlt User represents the source of a generated Dlt message. Possible users are Applications, RTE or other software modules
|Log Message| A Log Message contains debug information like state changes or value changes.
|Trace Message| A Trace messages contains information, which has passed via the VFB.
|ECU ID| The ECU ID is the name of an ECU, composed by 8-bit ASCII characters (e.g. "ABS0" or "InstrumentCluster").
|Session| A session is the logical entity of the source of log or trace messages. If a SW-C / application is instantiated several times, a session for each instance with a globally unique session ID is used.
|Session ID| The Session ID is the identification number of a log or trace session
|Application ID| Application ID is the name (or the abbreviation of it) of a SW-C / application. It identifies the SW-C / application that log and trace message originates.
|Context ID |Context ID is a user defined ID to group Log and Trace Messages generated by a SW-C / application. The following rules apply: * Each Application ID can own several Context IDs. * Context IDs are grouped by Application IDs. * Context IDs shall be unique within an Application ID. * The source of a log and trace message is identified using the tuple “Application ID” and “Context ID”. 8-bit ASCII characters compose the Context ID.
|Message ID| Messaged ID is the ID to characterize the information, which is transported by the message itself. A Message ID identifies a log or trace message uniquely. It can be used for identifying the source (in source code) of a message and it can be used for characterizing the payload of a message. A Message ID is statically fixed at development or configuration time and is used in conjunction with the "Non-Verbose Mode" (see later).
|Log level |A log level defines a classification for the severity grade of a Log Message.
|Trace status |The trace status provides information if a trace message should be sent.
|Log Channel| A physical Communications Bus which is used to transmit Dlt messages.
|External client| The external client is a tool to control, monitor and store the log/trace information provided by the ECUs using the Dlt module.
|string |For the Log and Trace Protocol a "string" defines a sequence of characters. Its length is either predefined by this document here, or there is a length specifier in front of it. The string contains only the character data for the text it represents without a special terminating item like the NULcharacter (\0).
|Verbose Mode| When the Dlt module is sending out Log and Trace information onto the communication channel, the sent data message contains also predefined, static data elements like names, units, format information, length and so on;
|Non-Verbose Mode|To reduce the network load on the communication channel, the Log and Trace data message contains as little of such metadata as possible. One of them is the Message-ID, which uniquely identifies this message and all of its content. All the above mentioned meta-data is handed over to the receiver via a separate extract file: together with the Message-ID, the receiver of a NonVerbose Mode message can reassemble the complete content, like sent in a Verbose Mode message.


# Reference

[1] Log and Trace Protocol Specification with protocol version "1" AUTOSAR_PRS_LogAndTraceProtocol from Release R20-11
[2] Information processing systems – Open Systems Interconnection – Basic Refer- ence Model
https://www.iso.org ISO/IEC 7498-1:1994
[3] Log And Trace Extract Template AUTOSAR_FO_TPS_LogAndTraceExtract
[4] IEEE Standard for Floating-Point Arithmetic (IEEE Std 754-2008)


Glossaryも掲載しましょう。
https://www.autosar.org/fileadmin/standards/R23-11/FO/AUTOSAR_FO_TR_Glossary.pdf



## 補足資料（Additions）
祝休日・謹賀新年：2024年の目標
https://qiita.com/kaizen_nagoya/items/b659d922327a7dcdc898

2023 Countdown Calendar 主催・参加一覧
https://qiita.com/kaizen_nagoya/items/c4c2f08ac97f38d08543

CountDownCalendar月間　いいねをいただいた記事群　views　順
https://qiita.com/kaizen_nagoya/items/583c5cbc225dac23398a

Countdown Calendar 2023, 百記事目を書くにあたって。
https://qiita.com/kaizen_nagoya/items/45185a04cfd88b71256a

1年間をまとめた「振り返りページ」＠２０２３
https://qiita.com/kaizen_nagoya/items/bcd1ebd49d3a9e8c7a90

AUTOSAR 文書番号
https://qiita.com/kaizen_nagoya/items/8b894228a0b76c2265c7

AUTOSAR Countdown Calendar 2023
https://qiita.com/advent-calendar/2023/autosar

＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
This article is an individual impression based on the individual's experience. It has nothing to do with the organization or business to which I currently belong.


# 文書履歴(document history)
ver. 0.01 初稿 　20240102
### 最後までおよみいただきありがとうございました。
いいね　💚、フォローをお願いします。
#### Thank you very much for reading to the last sentence.
Please press the like icon 💚　and follow me for your happy life.