KEI

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.

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.

I wrote Python code to simulate WriteDataByIdentifier. WriteDataByIdentifier is often protected by session and security, so the main test is to test it.

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.

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.