How to add diagnostic frames manually

The UDS diagnostic frame sending environment is the same as the previous CAN frame, and is also divided into two methods: manual addition and Cdd file import.

■Manually add diagnostic frames

1. Add a BasicDiagnosticECU

1. After adding

ECU qualifier: This is used when sending UDS diagnostic data using CAPL scripts. It does not need to be paid attention to when sending diagnostic frames manually.

Diagnostics tester: Select physical request or functional request. Physical request is selected by default.

The difference between physical requests and functional requests will be introduced separately in the UDS column later.

1. Set Transport Layer parameters

Request to ECU: ECU physical address Req ID

Response from ECU: ECU physical address Res ID

Functional to ECU: Functional addressing Req ID

STmin: TP layer protocol parameter, the interval between two consecutive frames sent

BlockSize: TP layer protocol parameter, the number of consecutive frames that can be sent after receiving the flow control frame. When set to 0, there is no limit on the number of frames sent.

FC Delay: The delay time for CANOe to reply to the flow control frame after receiving the first frame or continuous frames. The purpose is to prevent CANoe's flow control frame from replying too quickly, causing the receiving end to fail.

Max.Length: Maximum amount of data transmitted in one frame (first frame + consecutive frames)

Mixing of CAN2.0 and FD frames: Whether CAN frames and CAN-FD frames are compatible.

Ignore: Default value, incompatible. For example, when configured as CAN frame, CANOe does not accept CAN-FD frame, and the same is true when configured as CAN-FD frame.

Accecpt: Compatible, for example, when configured as CAN frame, CANOe can accept CAN-FD frame and return CAN frame.

Adapt: ​​Compatible, for example, when configured as CAN frames, CANOe can accept CAN-FD frames and return CAN-FD frames.

1. Configuring Diagnostic Layer Parameters

Send test present: Whether CANOe automatically sends 3E service for session maintenance

S3 Client time: The interval at which CANOe automatically sends 3E services

S3 Server time: The maximum time that the lower-level program remains in a session other than Default without receiving any diagnostic request

P2 Server: The time interval from when the lower computer program receives the Request to when it starts to reply to the Response

P2 Client: The time interval from when the host program sends a Request to when it receives a Response.

P2 extended Server: The time interval from when the lower computer sends NRC78 to the next reply Reponse

P2 extended Client: The time interval from when the host computer receives NRC78 to when it receives the next response

Seed&Key DLL: used to unlock 27 services and call. The .dll automatically calculates the value of Key. This .dll file is provided by the car manufacturer or Tier1

1. Additional Descriptions No configuration required

2. Add the required diagnostic services (taking $10 02 ProgrammingSession as an example)

a. Click Basic Diagnostic to open the panel

b. Right-click the service to be added and select [Add New Service]

c. Configure the sub-service's Req

Service Name: This is used during CAPL programming and does not require attention when sending diagnostic data manually.

d. Configure Response

Add or delete parameters in [Parameters] according to the expected format.

1. Open the Diagnostic Console

1. Click [Start] to send the diagnostic command just added in the Diagnostic Console.