DoCAN

I wrote Python code for simulation of ReadDataByIdentifier. Test pattern main related to ReadDataByIdentifier multi-DID. Multi-DID. Mix unsupported DIDs. Specify DIDs such that the response message length exceeds the maximum value.

Check the results of the TesterPresents simulation. Verification of messages. Checking the CAN line log. TesterPresents with suppressPosRspMsgIndicationBit is a special AUTOSAR-Dcm specification. After S3 time extension in Dsl, the message is discarded and not passed to Dsd and Dsp. The result is different from ISO14229-1, but the practicality is more important.

I wrote a Python code to simulate TesterPresents. Considering the main purpose of TesterPresents, SessionControl and SecurityAccess are also implemented. The main purpose is to suppress S3 timeouts.

Check the results of the SecurityAccess simulation. Check the message level. Check the CAN line level. SecurityAccess behavior depends on session state and security state. SecurityAccess behavior depends on session state, security state, and S3 timeout.

I wrote Python code for the SecurityAccess simulation. There is a large amount of work to be done to make sure SecurityAccess works. Support sessions. Sequence. Seed in security unlocked state. Transition to locked state on session transition. Session transitions due to S3 timeouts.

Check the results of the DiagnosticSessionControl simulation. Confirmation of message level. Confirmation of CAN line level. NegativeResponse can be automatically determined and returned by Dcm or by adding your own code. Message length and parameter abnormality are judged automatically. Rejections due to vehicle status are returned with an original code.

I wrote a Python code for simulation of DiagnosticSessionControl. Communication patterns include error patterns. Non-existent session. Wrong message length for a DiagnosticSessionControl request.

Review of AUTOSAR Dcm simulation configuration The Python code on the off-board tester side is the same as we have used so far. Modifications will be made as needed. The order in which the simulations are run is as follows. DiagnosticSessionControl. SecurityAccess. TesterPresent. ReadDataByIdentifier. WriteDataByIdentifier.

I wrote the configuration code for Dsp. Mostly security, session definition and association with DID.

Dsp is the application layer. It is divided into ISO14229-1 dependent and manufacturer dependent, and manufacturer dependent is handled by callback functions. The DID-related part of Dsp is the most complicated. Once you know DID, other configurations are relatively easy.