Specification of FlexRay Network Management, AUTOSAR R22-11, CP, No.28
AUTOSAR Countdown Calendar 2022
2022/12/09日の投稿です。
AUTOSARが、今年の版、R22-11公開しました。公開行事の模様は
AUTOSAR R22-11 Release Event 20221208
下記は想定URLです。順次確認中です。
間違っていたら、いいね を押していただいて、コメント欄にご報告くださると幸いです。
編集リクエストが、構造的な変更をしている最中に、構造的な編集リクエストをしていただくと、
何をどう直したらいいかわからなくなってしまいます。自動修復ツールがつくれていません。ごめんなさい。
文書は検索してダウンロードすることができます。
クラウドサービスにありがちな、あるのにないかのような検索結果が出ることがあります。
AUTOSAR R22-11 Qiita 記事一覧はこちらに編集中です。
<この項は書きかけです。順次追記します。>
用語(terms)
| Term | Description |
|---|---|
| CC | Communication Controller |
| NM | Network Management |
| WCET | Worst Case Execution Time |
| DET | Default Error Tracer. AUTOSAR Module for detection and reporting of errors during development. |
| SRS | Software requirements specification |
| SWS | Software working specification |
| API | Application program interface |
| Com | Communication module |
| OS | Operating system |
| SchM | Schedule Manager |
| PDU | Protocol data unit |
| CPU | Central processing unit |
| PNL | Partial Network Learning |
| FrIf | Abbreviation for the FlexRay Interface |
| FrNm | Abbreviation for the Network Management on FlexRay |
| NmIf | Abbreviation for the generic Network Management |
| ECU | Electronic control unit |
| ComM | Communication manager |
| FrSm | FlexRay State Manager |
| HW | Hardware |
| Bus-Sleep Mode | Network mode where all interconnected communication controllers are in the sleep mode. |
| NM-Network | Instance of the FlexRay NM to handle one physical FlexRay Bus. Caution: The FlexRay Bus contains two FlexRay channels which cannot be handled independent of the other. Therefore the NM-Network covers both FlexRay bus channels. This is equivalent to one NM-Cluster |
| Network requested | NM network is requested if FrNm_NetworkRequest has been called and neither the network has been released nor Bus Sleep Mode has been entered afterwards |
| Network released | NM network is released if FrNm_NetworkRelease has been called and network has not been requested afterwards |
| Repeat Message Request active | A Repeat Message Request is active if FrNm_RepeatMessageRequest has been called or a NM PDU with Repeat Message Request bit set has been received in Network Mode. It is not active anymore if Repeat Message State is left or Bus Sleep Mode is entered. |
| NM Data Cycle | Number of FlexRay cycles necessary for all nodes to be able to send NM Data at least once. |
| NM Message | Packet of information exchanged for purposes of the NM algorithm. |
| NM Repetition Cycle | Number of FlexRay cycles where no change of voting behavior is possible. Value has to be a multiple of the NM Voting Cycle. Used to |
| improve the reliability of the voting. | |
| NM Slot | Slot reserved for purposes of network management. |
| NM Timeout | Timeout in the NM algorithm that initiates transition into Bus-Sleep Mode. |
| NM User Data | Supplementary application specific data that is sent independent of the NM Vote on the bus. |
| NM Voting Cycle | Number of FlexRay cycles necessary for all nodes to vote at least once. NM-Vote Information transmitted using the FlexRay Bus indicating the vote of a ECU to keep the bus awake |
| NM-Vector | FlexRay NM Vector is the aggregated data available when the FlexRay CC optional NM Hardware Vector Service is used. |
| NM-Data | Data related to NM transmitted using the FlexRay Bus. |
| NM-Cluster | Obsolete, equivalent to NM-Network |
| CBV | Control bit vector |
| ClusterAwakeVote | At least one Node other than itself votes for keeping the cluster awake. |
| Positive NMVote in static segment | NM-Vote PDU reception or transmission with Voting Bit set to '1' |
| Positive NMVote in dynamic segment | NM-Vote PDU received or transmitted |
| Negative NMVote in static segment | NM-Vote PDU reception or transmission with Voting Bit set '0' |
| Negative NMVote | In dynamic segment: NM-Vote PDU is neither received nor transmitted |
| Top-level PNC coordinator | The top-level PNC coordinator is an ECU that acts as PNC gateway in the network and that handles at least one PNC as actively coordinated on all assigned channels. If synchronized PNC shutdown is enabled, the toplevel PNC coordinator triggers for these PNCs the shutdown, if no other ECU in the network request them. |
| Intermediate PNC coordinator | An intermediate PNC coordinator is an ECU that acts as PNC gateway in the network and that handles at least one PNC as passively coordinated on at least one assigned channel. If synchronized PNC shutdown is enabled, it forwards received shutdown requests for these PNCs to the corresponding actively coordinated channels and starts their shutdown accordingly. |
| PNC leaf node | A PNC leaf node is an ECU that acts not as a PNC coordinator at all in the network. It processes PN shutdown message as usual NM messages. |
| PN shutdown message | A top-level PNC coordinator transmit PN shutdown messages to indicate asynchronized PNC shutdown across the PN topology. A PN shutdown message is as NM message which has PNSR bit in the control bit vector and all PNCs which are indicated for a synchronized shutdown set to '1'. |
英日単語帳
日本語は仮訳
T.B.D.
参考(reference)
[1] List of Basic Software Modules
AUTOSAR_TR_BSWModuleList.pdf
[2] Layered Sofware Architecture,
AUTOSAR_EXP_LayeredSoftwareArchitecture.pdf
[3] General Requirements on Basic Software Modules
AUTOSAR_SRS_BSWGeneral.pdf
[4] Requirements on Network Management
AUTOSAR_SRS_NetworkManagement.pdf
[5] Specification of the AUTOSAR Network Management Protocol
AUTOSAR_PRS_NetworkManagementProtocol.pdf
[6] General Specification of Basic Software Modules
AUTOSAR_SWS_BSWGeneral.pdf
[7] Specification of SystemTemplate
AUTOSAR_TPS_SystemTemplate
[8] FlexRay Communications System Specifications, V2.1
[9] AUTOSAR Specification of Communication Manager
AUTOSAR_SWS_COMManager.pdf
[10] Specification of Generic Network Management Interface
AUTOSAR_SWS_NetworkManagement.pdf
[11] Specification of FlexRay Interface
AUTOSAR_SWS _FlexRayInterface.pdf
[12] Specification of ECU State Manager
AUTOSAR_SWS_ECUStateManager.pdf
[13] Specification of Default Error Tracer
AUTOSAR_SWS_DefaultErrorTracer.pdf
[14] Specification of Standard Types
AUTOSAR_SWS_StandardTypes.pdf
[15] Specification of Platform Types
AUTOSAR_SWS_PlatformTypes.pdf
[16] Specification of Compiler Abstraction
AUTOSAR_SWS_CompilerAbstraction.pdf
[17] Specification of Operating System
AUTOSAR_SWS_OS.pdf
[18] Specification of FlexRay State Manager
AUTOSAR_SWS_FlexRayStateManager.pdf
Glossary も 参考に入れましょう。
https://www.autosar.org/fileadmin/standards/foundation/22-11/AUTOSAR_TR_Glossary.pdf
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)
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の仕組みと設計のために
更新資料 Abstract Platform, Vehicle Modelへの対応版
Specification of FlexRay Network Management, AUTOSAR R22-11, CP, No.28(2)
＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
文書履歴(document history)
ver. 0.01 初稿 20221209
ver. 0.02 URL修正 20221221
ver. 0.03 Countdown Calendar 変更 20230106