PEAK-System Forum

Hello:
I have encounter a issue with the Peak-TP package, the gap time between First Frame and Flow Control is about 12ms, thus the Peak-TP API Read return with error 2 wait flow control timeout, so I want to know is there a API to increase the timeout value to adapt to my ECU server.
Yes, I have read the document, I can't find such kind of API, can you tell me how to fixed this issue as I can't increase my ECU server response time.

Hello,

Those default timeouts (defined in ISO-15765-2) are set to 1s, so I don't think your issue is related to this. A more common problem is related to the ISO-TP mappings: if you define only a single mapping from your test equipment to the ECU you will be able to send the First Frame of the CANTP message but won't receive the Flow Control from the ECU resulting in a network error n°2 (PCANTP_N_TIMEOUT_Bs).

That is why in PCTPClient for instance you'll see that there is always 2 mappings defined to test communication :

Code: Select all

// Mapping communication from Client to ECU
        CANTP_AddMapping(Channel, 0xA1, 0xA2,
		PCANTP_ID_CAN_11BIT, PCANTP_FORMAT_NORMAL, PCANTP_MESSAGE_DIAGNOSTIC,
		N_SA, N_TA_PHYS, PCANTP_ADDRESSING_PHYSICAL, 0x00);
// Mapping communication from ECU to Client
	CANTP_AddMapping(Channel, 0xA2, 0xA1,
		PCANTP_ID_CAN_11BIT, PCANTP_FORMAT_NORMAL, PCANTP_MESSAGE_DIAGNOSTIC,
		N_TA_PHYS, N_SA, PCANTP_ADDRESSING_PHYSICAL, 0x00);

Yeah:
That's the issue, I just call the mapping once as I think mapping once is enough.

PEAK-System Forum

CAN TP Timing parameter set

CAN TP Timing parameter set

Re: CAN TP Timing parameter set

Re: CAN TP Timing parameter set