モデルベース開発

車両診断通信

[CAN-FD] Vehicle Diagnostic Communication Part 90 [python-can 4]

Click here for back issues. Introduction. Explanation of CAN-FD simulation in python-can.This is the time to replay with...
車両診断通信

[CAN-FD] Vehicle Diagnostic Communication Part 89 [python-can 3]

It was discovered that can.player and can.logger do not support CAN-FD. I immediately modified them to support CAN-FD. can.logger has a little different problem.
車両診断通信

[CAN-FD] Vehicle Diagnostic Communication Part 88 [python-can 2]

Review can.player and can.logger. Created asc file for CAN-FD and CAN mixed replay. Mixed CAN is for identifying the affected area in case of an anomaly.
車両診断通信

[CAN-FD] Vehicle Diagnostic Communication Part 87 [python-can 1]

BusMaster does not support CAN-FD. The asc format of CAN-FD is different from CAN. FDF bit and BSR bit parameters are added.
車両診断通信

[CAN-FD] Vehicle Diagnostic Communication Part 86 [Overview 2]

Simulation procedure and intuition explanation. CAN-FD control with python-can. CAN-FD diagnostic communication with can-isotp (ISO15765-2). CAN-FD diagnostic communication with AUTOSAR-CanTp (ISO15765-2). AUTOSAR-Dcm for CAN-FD diagnostic communication (ISO14229-1).
車両診断通信

[CAN-FD] Vehicle Diagnostic Communication Part 85 [Overview 1]

Switch from CAN to CAN-FD for the physical and data link layers. CAN-FD is described in Vector's "CAN/CAN-FD for Beginners".
車両診断通信

[Dcm] Vehicle Diagnostic Communication Part 84 [Simulation 23]

We saw a pattern of returning NRC$10 (generalReject) when NRC$78 (ResponsePending) exceeds a certain number of times. This specification is not specified in ISO 14229-1. However, it is likely to be a de facto standard. Therefore, it is assumed that it is incorporated as an AUTOSAR specification.
車両診断通信

[Dcm] Vehicle Diagnostic Communication Part 83 [Simulation 22]

Check the results of the WriteDataByIdentifier simulation. Confirmation of the message. Confirmation of CAN line. Often used in conjunction with ReadDataByIdentifier to check operation for reading after writing. NRC$78 returned atmosphere. In fact, NRC$78 is rarely followed three times.
車両診断通信

[Dcm] Vehicle Diagnostic Communication Part 82 [Simulation 21]

I wrote Python code to simulate WriteDataByIdentifier. WriteDataByIdentifier is often protected by session and security, so the main test is to test it.
車両診断通信

[Dcm] Vehicle Diagnostic Communication Part 81 [Simulation 20]

Check the results of the ReadDataByIdentifier simulation. Confirmation of the message. Check CAN line logs. Multi-DID specification is tricky. A request for a non-existent DID is an error. However, if the DID exists in the multi-DID, it is not an error. If the DID exists, it is not an error. However, an error may occur due to the response message length.