ISO14229

車両診断通信

[DoCAN] Vehicle Diagnostic Communication Part 5 [ISO-TP 1]

There are physical addresses for one-to-one communication and functional addresses for one-to-many communication.Physical and functional addresses are composed of four different addressing formatsThe addressing formats consist of N_AI, N_TAtype, N_TA, N_SA, and N_AE.However, they may or may not be used depending on the addressing format.
車両診断通信

[DoCAN] Vehicle Diagnostic Communication Part 4 [CAN 3]

To determine the sampling points, the number of quantums in each segment must be determined.There are 4 types of segments, each for 1 bit.Synchronization Segment.Propagation Segment.Phase Segment1.Phase Segment2.Propagation Segment + Phase Segment1 is called tseg1, and Phase Segment2 is called tseg2
車両診断通信

[DoCAN] Vehicle Diagnostic Communication Part 3 [CAN 2]

Basically, a Google search can provide information on the CAN data link layer.CAN baud rate setting is special.It is not possible to set the baud rate directly, but the quantum time, which is a decomposition of 1 bit, is determined first.Since the total quantum is the baud rate, it is necessary to calculate backward from the baud rate you want to set.CAN can adjust the sampling point.It can be decided at which quantum in the total quantum to sample.This is often expressed as [%].50[%] for the middle, 75[%] for slightly behind (around 3/4).
車両診断通信

[DoCAN] Vehicle Diagnostic Communication Part 2 [CAN 1]

The required standard numbers were reviewed.CAN has become a relatively common specification, and you can find information there on the Internet and in books.1 Mbps is not often used in DoCAN.For legal reasons1Mbps lacks stability in some aspects.
車両診断通信

[DoCAN] Vehicle Diagnostic Communication Part 1 [Overview]

The typical standards for vehicle diagnostic communication are ISO 15765-2 and ISO 14229-1.Depending on the manufacturer's policy, the standard number may be a requirement rather than a specific requirement.The layers of vehicle diagnostic communication can be represented by the OSI model.There are two main axes of vehicle diagnostic communication.UDS and OBD.OBD is referenced by vehicle emission regulations, so the various parameters are clear.UDS only has recommended values, and the actual values are dependent on the finished vehicle manufacturer.
車両診断通信

車両診断通信【バックナンバー】

車両診断通信についていろいろ語っていく系のバックナンバー。DoCAN概要。CAN。ISO-TP。CanTpシミュレーション。UDS。Dcmシミュレーション。CAN-FD概要。python-canでCAN-FD。CAN-FDのISO-TP。CAN-FDでAUTOSAR。
車両診断通信

【たぶん最終回】車両診断通信 その100【振り返り】

たぶん最終回。簡単に振り返りをやってみる。車両診断通信はユースケースが多岐に分かれるという特性上話もその分広くなる。反面。XCPなどは開発に特化している。本シリーズは一旦終了。
車両診断通信

【CAN-FD】車両診断通信 その99【AUTOSAR③】

AUTOSARでのCAN-FDのシミュレーションの実施と結果。AUTOSAR-Dcmのシミュレーション実施。メッセージ最大長が変わるくらいで基本は同じ。AUTOSAR-CanTpのシミュレーション実施。リクエスト、レスポンスともにCAN-FDのルールに則った振る舞いをしていた。
車両診断通信

【CAN-FD】車両診断通信 その98【AUTOSAR②】

AUTOSARでのCAN-FDのシミュレーションに向けて。AUTOSAR-CanTpとAUTOSAR-Dcmのコンフィグレーションを修正。AUTOSAR-CanTpのコンフィグレーションをCAN-FD用に修正。AUTOSAR-DcmのコンフィグレーションをCAN-FD用に修正。
車両診断通信

【CAN-FD】車両診断通信 その97【AUTOSAR①】

AUTOSAR-CanTpとAUTOSAR-DcmのCAN-FDシミュレーションは一括でやってしまう方針。CanTpをr4.xのA-ComStackを使用していたのはCAN-FDに対応するため。(伏線回収!)シミュレーション構成はCANの時と全く一緒。レイヤードアーキテクチャの恩恵。