[DoCAN] Vehicle Diagnostic Communication Part 47 [UDS 8]

There are five services to be realized by UDS simulation DiagnosticSessionControl. SecurityAccess. TesterPresent. ReadDataByIdentifier. WriteDataByIdentifier. When explaining the request and response messages, the CAN frame is not explained. I will only explain the ISO 14229-1 layer and not the ISO 15765-2 layer.

[DoCAN] Vehicle Diagnostic Communication Part 46 [UDS 7]

Presentation of the overall structure of the USD simulation. A-COMSTACK is AUTOSAR r3.x series and OpenSAR is AUTOSAR r4.x series. Therefore, illegal construction.

[DoCAN] Vehicle Diagnostic Communication Part 45 [UDS 6]

Click here for back issues.Introduction.Explanation of ISO 14229, or UDS.This time, the open source AUTOSAR, which is di

[DoCAN] Vehicle Diagnostic Communication Part 44 [UDS 5]

Routine explanation. Mainly used for functions such as those used during development. Explanation of Upload/Download. A group of services for data transfer that can also compress and encrypt data.

[DoCAN] Vehicle Diagnostic Communication Part 43 [UDS 4]

Stored Data Transmission Description. Getting and clearing DTC and freeze data. Description of Input/Output Control. I/O control of ECU. While convenient, this service can be dangerous depending on the condition of the vehicle,so it is necessary to consider safety functions.

Windows10でフォトが消えた。というかストアも消えてた。ってところからの復旧

PowerShellを管理者権限で起動し、ストアを削除＆再インストール。 ストアからフォトをインストール。 なぜ消えたかは不明。

[DoCAN] Vehicle Diagnostic Communication Part 42 [UDS 3]

Diagnostic services fall into six categories of functional units. Diagnostic and Communications Management explained. Session, Security, and Communications Control. Data Transmission Description. Read/write data by memory address and DID.

[DoCAN] Vehicle Diagnostic Communication Part 41 [UDS 2]

P2 time is explained with figures. P2* timeout will be explained later. S3 time is explained with figures. S3 time is explained in detail. It is difficult if you don't know the various services.

[DoCAN] Vehicle Diagnostic Communication Part 40 [UDS 1]

Click here for back issues.Introduction.I will start explaining ISO 14229 (UDS) from this time.Vehicle Diagnostic Commun

[CanTp] Vehicle Diagnostic Communication Part 39 [Simulation 27]

Click here for back issues.Introduction.Let's simulate ISO-TP. Series of.Continuation of the times to simulate.This

[CanTp] Vehicle Diagnostic Communication Part 38 [Simulation 26]

Review of simulation configuration. Code handling on the virtual ECU side. Currently, it's private, give me a break. Confirmation of communication logs of SF-SF, SF-MF, and MF-MF.

[CanTp] Vehicle Diagnostic Communication Part 37 [Simulation 25]

Fixed the script for Python can-isotp requests. The request is now ISO14229-1 compliant. Implemented AUTOSAR-CanTp side. The response is now SO14229-1 compliant as well. The code has not been published yet for personal reasons.

[CanTp] Vehicle Diagnostic Communication Part 36 [Simulation 24]

We defined a concrete configuration structure for AUTOSAR-CanTp. The number PduId is used when interacting with CanIf. In this case, the following. 0: Transmission of 0x18DAF110. 1: Receipt of 0x18DA10F1. 2: Transmission of 0x18DA10F1. 3: Receipt of 0x18DAF110. The Receive Control Block for CH_RX_CB and the Transmit Control Block for CH_TX_CB are for work.

[CanTp] Vehicle Diagnostic Communication Part 35 [Simulation 23]

The configuration structure of CanTp is described in the AUTOSAR specification. However, there is no UML description. The update priority may have been lowered since it has been followed since the OSEK era. This time, we will define the corresponding structure entity manually without using a configurator.

[CanTp] Vehicle Diagnostic Communication Part 34 [Simulation 22]

CanTp is based on the concept of a pair of transmitting and receiving channels. Channels can be duplicated. However, dynamic duplication is not allowed. Only static duplication is possible.

Windows10(64bit)でMATLAB 2012b のmex setup(コンパイラ環境構築)

※ レジストリをいじるので、本記事をもとに作業する場合は自己責任でお願いします。 MATLAB 2012bの64bitコンパイラ環境はVisual C++ 2010にする必要があるのだが、 Windows10においてはVisual C++ 2010且つ64bitコンパイラを用意するのはかなり難儀した。 自分自身の忘備録として残しておく。

[CanTp] Vehicle Diagnostic Communication Part 33 [Simulation 21]

Review of AUTOSAR CanTp interfaces. I have drawn a figure of the interfaces of AUTOSAR CanTp. Each interface is defined in its own header file. But they need to be reconciled for simulation.

[CanTp] Vehicle Diagnostic Communication Part 32 [Simulation 20]

The AUTOSAR CanTp specification is published in AUTOSAR_SWS_CANTransportLayer. The minimum interfaces that need to be grasped are the following. CanTp_Transmit. CanTp_MainFunction. CanTp_RxIndication. CanTp_TxConfirmation. CanIf_Transmit. PduR_CanTpCopyRxData. PduR_CanTpCopyTxData. PduR_CanTpRxIndication. PduR_CanTpStartOfReception. PduR_CanTpTxConfirmation.

[CanTp] Vehicle Diagnostic Communication Part 31 [Simulation 19]

The body of CanTp for A-COMSTACK is cantp.c. Many header files also need to be brought in. Timer interrupt and exclusion are realized by Win32API.

[CanTp] Vehicle Diagnostic Communication Part 30 [Simulation 18]

A-COMSTACK, a set of communication stack BSW for AUTOSAR, is released by the TOPPERS Association. CanTp is used in this stack. A-COMSTACK can only be used commercially if you are an AUTOSAR partner. This time, it is used for learning purpose. The off-board tester side for operation check uses python can-isotp.

[CanTp] Vehicle Diagnostic Communication Part 29 [Simulation 17]

The code for interrupt emulation is presented. Wait for signal with WaitForSingleObject. xlCanReceive to get various information on receive, send, and error. xlEvent.tag allocates to various processes.

[CanTp] Vehicle Diagnostic Communication Part 28 [Simulation 16]

To realize MCAL-CANDRV, it is necessary to reproduce the receive and transmit completion interrupts. The XL driver library notifies the events of received, sent, and error via Win32API event object. Therefore, knowledge of thread and event object handling by Win32API is required.

[CanTp] Vehicle Diagnostic Communication Part 27 [Simulation 15]

We are now in the AUTOSAR CanTp section! AUTOSAR has a layered structure of SW-C, RTE, BSW, and MCAL. AUTOSAR CanTp is one of BSW and reproduces ISO 15765-2.

[CanTp] Vehicle Diagnostic Communication Part 26 [Simulation 14]

We experimented with changing FC parameters in can-isotp. can-isotp is highly complete. At least, it is much better than those vehicle diagnostic communication whose structure is broken.

[CanTp] Vehicle Diagnostic Communication Part 25 [Simulation 13]

We experimented with can-isotp request-response. SF-SF communication -> OK! MF-MF communication -> OK!

[CanTp] Vehicle Diagnostic Communication Part 24 [Simulation 12]

Most vehicle diagnostic communication is a single request-response communication. There are some exceptions such as request-only and response-only communication, but they are quite rare. Both the request and response sides are script fatted by the receive thread mechanism.

[CanTp] Vehicle Diagnostic Communication Part 23 [Simulation 11]

I changed the FC equivalent to change the behavior of can-isotp multi-frame requests. The behavior is now compliant with the specified STmin. The time parameters for communication are wide enough to allow for synchronization between systems. If it is more than 10[ms], we aim for 11[ms] to ensure that it meets 10[ms] or more.

[CanTp] Vehicle Diagnostic Communication Part 22 [Simulation 10]

In the default state of can-isotp, the DLC optimization specification is adopted. If you set padding and MIN_DLC in the parameters passed to CanStack, it switches to the padding specification.

[CanTp] Vehicle Diagnostic Communication Part 21 [Simulation 9]

The FC's add up in python-can. Supported by inserting CAN frames with a bit of timing in python-can. This allowed the multi-frame request to go through for now.

[CanTp] Vehicle Diagnostic Communication Part 20 [Simulation 8]

The Python package can-isotp can communicate ISO15765-2, or ISO-TP. However, python-can must also be installed due to dependencies. For now, SF (SingleFrame) transmission is possible. The multi-frame transmission stopped at FF (FirstFrame) and ended in an error. The protocol specification is that the next sequence cannot proceed unless FC is received after FF.

[CanTp] Vehicle Diagnostic Communication Part 19 [Simulation 7]

Listed the devices supported by python-can. Sending/receiving by python-can was realized.