PEAK-System Forum

Hello
I am writing an ECU software software with PCAN-UDS API.
I almost implemented update protocol, but there is a issue.

As I know, the tester(in my case, update software in my PC) sets N_Cs delay time to the value of Minimum Separation Time (STMIN) in the flow control message. Unfortunately, there is a case that both target ECU and Gateway just send this value to ZERO even the GW doesn't support this speed.

I tried to use SetValue() API to change the STMin value. But when I analyzed the log, N_Cs is still less than 1ms.
I am currently using PCAN-UDS / ISO-TP / PCAN-BASIC API and PEAK-USB device. I just downloaded library and driver yesterday from the website.

Is there any solution?

Hello,

the Separation Time (STmin) and the block size are parameters defined by the receiver (in your case the ECU/Gateway) and not by the sender (the Tester, i.e your update software).

A value of Zero means that the tester can sent packages as fast as it can to the ECU. The tester cannot command the ECU to use another value. Try changing the settings of the ECU/Gateway.

Dear K.Wagner
Thank you very much for your response.

As you mentioned, I know that that value is determined by the receiver.
What I want to do is to delay the speed of TP transfer even the ECU returns STMin value to zero because we have some internal issues that we can't change ECU's software.

Does PCAN-UDS ans TP API have any APIs that force that delay?

Thank you very much.

Hello,

hcyang1012 wrote:Does PCAN-UDS ans TP API have any APIs that force that delay?

Unfortunately not. The PCAN-ISO-TP and PCAN-UDS APIs strictly follow the protocol specifications and this would breakup the rules.

hi support
I'm unable to understand what files should we include on the client-side and server-side. We are developing UDS protocol stack.

Can you specify the Client-side and server-side APIs? We are using the TI F280049C series. All our development is in C programming language and the APIs are in C++ or C#. Kindly guide us.

Hello,

for clarification, please note that the PCAN-UDS API is written generally, i.e., there are no different files for using with a client or a server application.
Generally, a client is the PC application that uses PCAN-UDS and the server is any electronic control unit. You need the API files there where you are accessing the PCAN-UDS.dll library (i.e. where your application is running).

Using PCAN-UDS implies using PCAN-ISO-TP and PCAN-Basic too. See the chapter "Understanding PCAN-UDS 2.x" in page 11 of the PCAN-UDS documentation for more details.

REMARK: Please next time open a new topic for your question. It has nothing to do with the problematic discussed here.