Can confirm client wasn't emitting correct CTS due to malformed First Frame by server (incorrect DL, byte 2).
Works as intended now.
Search found 3 matches
- Tue 5. Mar 2024, 17:29
- Forum: PCAN-UDS
- Topic: MSGPROTOCOL_FIXED_NORMAL no ISO TP flow control
- Replies: 4
- Views: 2632
- Tue 5. Mar 2024, 16:22
- Forum: PCAN-UDS
- Topic: MSGPROTOCOL_FIXED_NORMAL no ISO TP flow control
- Replies: 4
- Views: 2632
Re: MSGPROTOCOL_FIXED_NORMAL no ISO TP flow control
Michael, thanks for reaching out.
It seems like I have bare P-CAN USB adapter, without any s/n imformation, and packaging long gone.
How can we resolve this?
Flow control seems to work for other forum members, though they use 11bit IDs mainly.
It seems like I have bare P-CAN USB adapter, without any s/n imformation, and packaging long gone.
How can we resolve this?
Flow control seems to work for other forum members, though they use 11bit IDs mainly.
- Tue 5. Mar 2024, 12:19
- Forum: PCAN-UDS
- Topic: MSGPROTOCOL_FIXED_NORMAL no ISO TP flow control
- Replies: 4
- Views: 2632
MSGPROTOCOL_FIXED_NORMAL no ISO TP flow control
Please, help me with resolving the following problem:
I am using PCAN-UDS trying to receive both ISO-TP and sigle frame responses to UDS services (in this case, RequestScalingByIdentifier).
Config is the following:
29bit CAN ID, J1939 format, server ID = 0x10, tester ID = 0x20, block size = 32 ...
I am using PCAN-UDS trying to receive both ISO-TP and sigle frame responses to UDS services (in this case, RequestScalingByIdentifier).
Config is the following:
29bit CAN ID, J1939 format, server ID = 0x10, tester ID = 0x20, block size = 32 ...