Search found 7 matches
- Mon 25. Sep 2017, 12:57
- Forum: PCAN-UDS
- Topic: Fail to receive message from ECU with 29bit CAN addressing
- Replies: 18
- Views: 26830
Re: Fail to receive message from ECU with 29bit CAN addressi
I can now receive UDS responses from my ECU!!! Many thanks. I had set the priority field to 7 as the priority field is set to 7 our project CAN messages. I thought I needed to set this. However it seems I did not need it set at all.
- Mon 25. Sep 2017, 10:58
- Forum: PCAN-UDS
- Topic: Fail to receive message from ECU with 29bit CAN addressing
- Replies: 18
- Views: 26830
Re: Fail to receive message from ECU with 29bit CAN addressi
Hi, I have set N_AI.PROTOCOL to PUDS_PROTOCOL_ISO_15765_2_29B_NORMAL but still not working.
UDS API version is: 1.3.0.25
PCAN-ISO API version is:2.0.1.82
I using 64 bit version of DLLs.
I have attached the PCAN trace of the ECU responding to UDS request
Kind Regards
UDS API version is: 1.3.0.25
PCAN-ISO API version is:2.0.1.82
I using 64 bit version of DLLs.
I have attached the PCAN trace of the ECU responding to UDS request
Kind Regards
- Thu 21. Sep 2017, 18:30
- Forum: PCAN-UDS
- Topic: Fail to receive message from ECU with 29bit CAN addressing
- Replies: 18
- Views: 26830
Re: Fail to receive message from ECU with 29bit CAN addressi
Thanks, I have not set it to 0xF9 but still no response.. I not sure what else it could be now
Have I got the N_AI set correctly in the below code?
// Define Address
iBuffer = 0xF9;
Status = UDS_SetValue(Channel, PUDS_PARAM_SERVER_ADDRESS, &iBuffer, 1);
printf(" Set ServerAddress: %i (0x ...
Have I got the N_AI set correctly in the below code?
// Define Address
iBuffer = 0xF9;
Status = UDS_SetValue(Channel, PUDS_PARAM_SERVER_ADDRESS, &iBuffer, 1);
printf(" Set ServerAddress: %i (0x ...
- Thu 21. Sep 2017, 17:33
- Forum: PCAN-UDS
- Topic: Fail to receive message from ECU with 29bit CAN addressing
- Replies: 18
- Views: 26830
Re: Fail to receive message from ECU with 29bit CAN addressi
The ECU address is 0x93 which I have set via PUDS_PARAM_SERVER_ADDRESS
I have defined the client address as 0xF9 using:
// Define Network Address Information used for all the tests
N_AI.SA = 0xF9;
N_AI.TA = 0x93;
N_AI.TA_TYPE = PUDS_ADDRESSING_PHYSICAL;
N_AI.RA = 0x00;
N_AI.PROTOCOL = PUDS ...
I have defined the client address as 0xF9 using:
// Define Network Address Information used for all the tests
N_AI.SA = 0xF9;
N_AI.TA = 0x93;
N_AI.TA_TYPE = PUDS_ADDRESSING_PHYSICAL;
N_AI.RA = 0x00;
N_AI.PROTOCOL = PUDS ...
- Thu 21. Sep 2017, 14:07
- Forum: PCAN-UDS
- Topic: Fail to receive message from ECU with 29bit CAN addressing
- Replies: 18
- Views: 26830
Re: Fail to receive message from ECU with 29bit CAN addressi
Thank you. I have tried this but still no uds response is reported.
- Thu 21. Sep 2017, 10:53
- Forum: PCAN-UDS
- Topic: Fail to receive message from ECU with 29bit CAN addressing
- Replies: 18
- Views: 26830
Re: Fail to receive message from ECU with 29bit CAN addressi
Hi, many thanks for your reply. I am using that this version already. I have modified the PCUClient sample app (x64) to work with my setup. Perhaps I done something wrong. I can see the UDS requests from the client are correct and my ECU sends a reply (I can see it in PCAN-View). Below is the code I ...
- Wed 20. Sep 2017, 18:11
- Forum: PCAN-UDS
- Topic: Fail to receive message from ECU with 29bit CAN addressing
- Replies: 18
- Views: 26830
Re: Fail to receive message from ECU with 29bit CAN addressi
Hi, I think I may have the same problem with receiving 29 bit IDs. My ECU is responding but the UDS API is reporting no data. Is there a beta version of the API that resolves this issue available? Many Thanks.
// 29 bit can ID, normal format addressing (diagnostic message mandatory) -
Status ...
// 29 bit can ID, normal format addressing (diagnostic message mandatory) -
Status ...