車両診断通信 [Probably the last article] Vehicle Diagnostic Communication Part 99 [Looking Back] Brief look back. The vehicle diagnostic communication has a wide range of use cases, which makes it a broad topic. This series is now over. 2023.02.24 車両診断通信
車両診断通信 [CAN-FD] Vehicle Diagnostic Communication Part 98 [AUTOSAR 3] Simulation of AUTOSAR-Dcm was executed. Simulation of AUTOSAR-Dcm, the basic principle is the same, except for the maximum message length. Simulation of AUTOSAR-CanTp. Both request and response behaved according to CAN-FD rules. 2023.02.23 車両診断通信
車両診断通信 [CAN-FD] Vehicle Diagnostic Communication Part 97 [AUTOSAR 2] Fixed the configuration of AUTOSAR-CanTp for CAN-FD. Fix configuration of AUTOSAR-Dcm for CAN-FD. 2023.02.22 車両診断通信
車両診断通信 [CAN-FD] Vehicle Diagnostic Communication Part 96 [AUTOSAR 1] Click here for back issues. Introduction. The policy for simulation of CAN-FD in AUTOSAR will be explained. Simulation P... 2023.02.21 車両診断通信
車両診断通信 [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). 2023.02.10 車両診断通信
車両診断通信 [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". 2023.02.09 車両診断通信
車両診断通信 [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. 2023.02.08 車両診断通信
車両診断通信 [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. 2023.02.07 車両診断通信
車両診断通信 [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. 2023.02.06 車両診断通信
車両診断通信 [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. 2023.02.05 車両診断通信