I have just find the issue : you were rigth, this is an issue on the message size, a regression has been recently introduced by another member of the team.
Thanks for tour help.
Search found 3 matches
- Tue 17. Aug 2021, 11:34
- Forum: PCAN-RP1210
- Topic: J1939 and DLC
- Replies: 3
- Views: 4073
- Tue 17. Aug 2021, 11:14
- Forum: PCAN-RP1210
- Topic: J1939 and DLC
- Replies: 3
- Views: 4073
Re: J1939 and DLC
Thanks for your quick response.
I checked the size of the data put into the fpchClientMessage parameter, it is 9 bytes long, according to what is specified in documentation.
This parameter is a scruture composed of :
unsigned char PGN[3]; //3 bytes
unsigned char priority; //1 byte
unsigned char ...
I checked the size of the data put into the fpchClientMessage parameter, it is 9 bytes long, according to what is specified in documentation.
This parameter is a scruture composed of :
unsigned char PGN[3]; //3 bytes
unsigned char priority; //1 byte
unsigned char ...
- Mon 16. Aug 2021, 14:02
- Forum: PCAN-RP1210
- Topic: J1939 and DLC
- Replies: 3
- Views: 4073
J1939 and DLC
Hello,
I'm using RP1210 API in C++ for a custom application.
When I send a message using RP1210_SendMessage with PGN 59904, I'm expecting to have a DLC of 3, but with a CAN analyser, I have à DLC of 8 with bitstufing by 0x00.
In the API, I can't find anywhere a way to tune the DLC.
As I can read ...
I'm using RP1210 API in C++ for a custom application.
When I send a message using RP1210_SendMessage with PGN 59904, I'm expecting to have a DLC of 3, but with a CAN analyser, I have à DLC of 8 with bitstufing by 0x00.
In the API, I can't find anywhere a way to tune the DLC.
As I can read ...