[Dcm] Vehicle Diagnostic Communication Part 62 [Simulation 1]

Click here for back issues.
https://www.simulationroom999.com/blog/diagnostic-communication-en-back-issue/

Introduction.
AUTOSAR-Dcm simulation configuration
Items to check in an AUTOSAR-Dcm simulation
Conclusion

Introduction.

In this article, I will explain the AUTOSAR-Dcm for the simulation of AUTOSAR-Dcm.

AUTOSAR-Dcm simulation configuration

Now that I have explained the necessary services, let’s review the AUTOSAR-Dcm simulation configuration again.

Overall UDS Simulation Configuration,Dcm is not multi-channel compatible due to specifications.Pre-emption specification seems to be implemented, but it is not used this time.Python,diagnostic request,isotp,python-can,can.logger,Virtual CAN BUS,exe,Test program ECU side,Dcm,CanTp,Channel(1),Transmission(1)18DAF110,Received(2)18DA10F1,CanDrv

See below for a detailed explanation.

[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.

The structure is supposed to be a combination of r3.x and r4.x systems, like an illegal building, but there should be no need to be so vigilant.
(Is it too much to ask you not to be alarmed?)

Items to check in an AUTOSAR-Dcm simulation

By the way, do you remember the services to be performed in an AUTOSAR-Dcm simulation?
I think I showed you the following table before.

Service	SID	Description
DiagnosticSessionControl	$10	Diagnostic session control
SecurityAccess	$27	Security unlocking
TesterPresent	$3E	Notification of the presence of an off-board tester. (Used for session keeping, etc.)
ReadDataByIdentifier	$22	Reading of the current value of the record identified by dataIdentifier
WriteDataByIdentifier	$2E	Writing of the record identified by dataIdentifier

The relevant article is below.

[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.

A brief summary is as follows.

TesterPresent(Service$3E)
- also check for presence of suppressPosRspMsgIndicationBit
ReadDataByIdentifier(Service$22)
- also checks for multi-DID
WriteDataByIdentifier(Service$2E)
- SessionControl(Service$10)/SecurityAccess(Service$27) also checked
- Also check S3 time
Check ResponsePending
- Also check responsePendingCount

Now you may be thinking, “What is responsePendingCount?”.
To be sure, I will not explain this.

It is not specified in ISO14229-1, but in practice, the number of possible replies to NRC$78 (ResponsePending) is often specified.
This specification is also in AUTOSAR-Dcm, so it’s a good time to check this as well.

It’s not a complicated matter.
Just change one parameter and see how it behaves.

Conclusion

AUTOSAR-Dcm simulation configuration review.
Review of services used in AUTOSAR-Dcm simulation.
- Listed specific items to be checked.
- Will also include confirmation of responsePendingCount, the number of times NRC$78 replies are received.

Click here for back issues.