Log and Trace Protocol Specification, AUTOSAR R22-11, FO, No.787
AUTOSAR Countdown Calendar 2022
2022/12/04日の投稿です。
AUTOSARが、今年の版、R22-11をまもなく公開します。
RELEASE EVENT 08-December-2022
下記は想定URLです。まだ公開していなければごめんなさい。
文書は、廃止になっていなければ、2022年12月8日(たぶんヨーロッパ時間)以降に検索してダウンロードできるはずです。
AUTOSAR R22-11記事一覧はこちら。
<この項は書きかけです。順次追記します。>
| Document Title | Log and Trace Protocol Specification |
|---|---|
| Document Owner | AUTOSAR |
| Document Responsibility | AUTOSAR |
| Document Identification No | 787 |
| Document Status | published |
| Part of AUTOSAR Standard | Foundation |
| Part of Standard Release | R21-11 |
Document Change R21 - 11
- Add support for specific format and precision coding (TYFM & TYPR).
- Fix "RestoreToFactoryDefault()" to "ResetToFactoryDefault()" and fixes in response parameter of "GetLogInfo()".
- Introduction of v2 of the protocol.
- Non-VerboseMessage-format-ARXML is now in TPS_LogAndTrace_Extract.
英日単語帳
日本語は仮訳
| no. | count | word | 日本語 |
|---|---|---|---|
| 1 | 1220 | the | その |
| 2 | 583 | of | の |
| 3 | 479 | and | と |
| 4 | 388 | prs_dlt_ | prs_dlt_ |
| 5 | 314 | type | 型 |
| 6 | 297 | id | identifier, 識別子(短縮名） |
| 7 | 292 | trace | 跡 |
| 8 | 286 | x | x |
| 9 | 285 | to | に |
| 10 | 278 | in | の中に |
| 11 | 270 | is | です |
| 12 | 258 | be | です |
| 13 | 258 | message | 伝言 |
| 14 | 243 | a | 一つの |
| 15 | 241 | log | 記録 |
| 16 | 230 | shall | しなければならない |
| 17 | 229 | for | にとって |
| 18 | 229 | rs_lt_ | rs_lt_ |
| 19 | 214 | protocol | 規約 |
| 20 | 202 | bit | binary digit(短縮名） |
| 21 | 173 | data | 与件 |
| 22 | 164 | name | 名前 |
| 23 | 157 | dlt | Diagnostic Log and Trace(短縮名） |
| 24 | 156 | length | 長さ |
| 25 | 139 | or | または |
| 26 | 137 | field | 分野 |
| 27 | 137 | number | 番号 |
| 28 | 136 | if | もし |
| 29 | 135 | header | 見出し |
| 30 | 129 | with | と |
| 31 | 119 | info | information(短縮名） |
| 32 | 108 | information | 情報 |
| 33 | 108 | set | 設定する |
| 34 | 107 | autosar | AUTomotive Open System Architecture(短縮名) |
| 35 | 98 | application | 応用 |
| 36 | 97 | specification | 仕様 |
| 37 | 97 | uint | unsigned integer（短縮名） |
| 38 | 96 | document | 資料 |
| 39 | 90 | r | r |
| 40 | 88 | description | 説明 |
| 41 | 85 | autosar_prs_log | autosar_prs_log |
| 42 | 84 | fo | foundation(短縮名) |
| 43 | 82 | payload | 負荷 |
| 44 | 80 | this | これ |
| 45 | 77 | used | 使った |
| 46 | 76 | unsigned | 符号なし |
| 47 | 75 | context | 文脈 |
| 48 | 69 | base | 基づく |
| 49 | 67 | an | 一つの |
| 50 | 65 | it | それ |
| 51 | 65 | reserved | 予約済み |
| 52 | 64 | level | 水準 |
| 53 | 63 | as | なので |
| 54 | 63 | e | e |
| 55 | 63 | ecu | Electronic Control Unit（短縮名） |
| 56 | 63 | string | 文字列 |
| 57 | 62 | are | です |
| 58 | 62 | following | 続く |
| 59 | 62 | not | いいえ |
| 60 | 62 | variable | 変数 |
| 61 | 61 | integer | 整数 |
| 62 | 59 | messages | 伝言 |
| 63 | 58 | by | に |
| 64 | 58 | extension | 拡大 |
| 65 | 58 | format | 書式 |
| 66 | 57 | verbose | 冗長 |
| 67 | 55 | source | 源 |
| 68 | 55 | value | 価値 |
| 69 | 54 | non | 非 |
| 70 | 52 | can | できる |
| 71 | 51 | mode | 状態 |
| 72 | 49 | all | すべて |
| 73 | 49 | status | 状態 |
| 74 | 48 | file | 紙ばさみ |
| 75 | 48 | service | 奉仕 |
| 76 | 47 | parameter | 引数 |
| 77 | 45 | added | 追加した |
| 78 | 44 | response | 応答 |
| 79 | 42 | dyn | Dynamic Length Signals(短縮名？） |
| 80 | 42 | on | の上 |
| 81 | 41 | byte | 束 |
| 82 | 41 | float | 浮く |
| 83 | 39 | error | 誤り |
| 84 | 39 | module | 部品 |
| 85 | 39 | that | それ |
| 86 | 39 | which | どの |
| 87 | 38 | case | 場合 |
| 88 | 38 | control | 制御 |
| 89 | 38 | note | 覚書 |
| 90 | 38 | request | 要求 |
| 91 | 38 | sint | signed integer(短縮名） |
| 92 | 37 | use | 使用する |
| 93 | 35 | at | で |
| 94 | 35 | floa | floating point(短縮名） |
| 95 | 35 | ids | identifiers, 識別子(短縮名） |
| 96 | 34 | defined | 定義済み |
| 97 | 33 | like | 好き |
| 98 | 33 | not_supported | not_supported |
| 99 | 33 | one | 1 |
| 100 | 33 | unit | 単位 |
dynが、何の短縮形かの記述がみあたらなかった。
dynamic length signalのビット数の大きさごとの型名で利用している。
short name
| short name | 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. |
Note
P.19
Note: "Network Byte Order" equals "Big Endian".
Reference
Glossary も 参考に入れましょう。
https://www.autosar.org/fileadmin/standards/foundation/22-11/AUTOSAR_TR_Glossary.pdf
[1] ISO/IEC 7498-1:1994 Information technology - Open Systems Interconnection - Basic Reference Model: The Basic Model - Part 1
[2] Log and Trace Protocol Specification v.1 AUTOSAR_PRS_LogAndTraceProtocol from release R20-11
[3] AUTOSAR Log And Trace Extract Template AUTOSAR_TPS_LogAndTraceExtract
Countdown Calendar 2022
今年企画した6つのCountdown Calendarと、それぞれの記事一つをご紹介します。
AUTOSAR Countdown Calendar 2022
AUTOSAR References to ISO, IEC, ITU, IEEE, RFC and SEA etc.
Automotive Handbook Countdown Calendar 2022
Basic principles, ボッシュ自動車handbook(英語)11版まとめ<2>
2022 いいねをいただいた記事ランキング(O.K.版) Countdown Calendar 2022
2022年１月下旬 いいねをいただいた記事 16
CDCale(O.K.) Countdown Calendar 2022
「会議は15分未満」に。小耳にはさんだ話。
ABC language (O.K.版） Advent Calendar 2022
LLVMソースコードのコンパイルをしようと思ってハマった罠とそこから脱出するための努力
ABC maker(O.K版） Advent Calendar 2022
JAXA/IPA クリティカルソフトウェアワークショップ WOCS言語関連発表(改定版)
CountdownCalendar2022 報告
関連文書(Related document)
AUTOSAR Abstract Platformへの道（詳細編）
2023年1月 記事数一覧
年末100記事を30点に仕上げる。
2023 書き初め
「はじめてのCAN/CANFD 」 ベクタージャパン ＜エンジニア夏休み企画>【読書感想文】
三方良し Udemy 車載LAN入門講座 CAN通信編
詳解 車載ネットワーク CAN, CAN FD, LIN, CXPI, Ethernetの仕組みと設計のために(1) 著者 ＜エンジニア夏休み企画 読書感想文＞
詳解 車載ネットワーク CAN, CAN FD, LIN, CXPI, Ethernetの仕組みと設計のために(2)参考文献 ＜エンジニア夏休み企画>【読書感想文】
詳解 車載ネットワーク CAN、CAN FD、LIN、CXPI、Ethernetの仕組みと設計のために
AUTOSAR Abstract Platform User Group Weekly Report(1) 2022.1.8
AUTOSAR Abstract Platform User Group Weekly Report(2) 2022.1.15
更新資料 Abstract Platform, Vehicle Modelへの対応版
Log and Trace Protocol Specification, No.787, FO, AUTOSAR R22-11 新
https://qiita.com/kaizen_nagoya/items/e0523ed6c7b55cbbbba2
＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
文書履歴(document history)
ver. 0.01 初稿 20221204
ver. 0.02 URL追記 20230131