Automotive and Embedded Networks

cancel
Showing results for 
Search instead for 
Did you mean: 

CAN read output showing different arbritration ID than sensor sends

Hello,

 

I am facing a very weird problem. I am building an application to read and log the CAN data from the angle sensor. I am able to do all the things that I want to.

But the problem is my sensor is sending CAN data with extended arbritration ID 0x18F01DE4 but in my LV application when I read it it shows 0x38F01DE4.

I cross checked it with MAX also and it shows the right ID i.e. 0x18F01DE4

 

Does anyone knows the reason behind this?

 

 

regards

swap

Message 1 of 5
(5,873 Views)
This is normal for the older CAN api. It shows the message is an extended message by adding 0x20000000
0 Kudos
Message 2 of 5
(5,862 Views)

correct. and well documented in the NI-CAN manual P11-47 😉

 

ArbitrationId = Returns the arbitration ID of the received data frame. The NCTYPE_CAN_ARBID type is an unsigned 32-bit integer that uses the bit mask NC_FL_CAN_ARBID_XTD (0x20000000) to indicate an extended ID. A standard ID (11-bit) is specified by default.The Network Interface receives data frames based on the comparators and masks configured in ncConfig (including the Series 2 Filter Mode attributes).

Message 3 of 5
(5,857 Views)

 

 

thanks ...............solved the problem....:-)

 

 

0 Kudos
Message 4 of 5
(5,852 Views)

swap15 wrote: 

 

thanks ...............solved the problem....:-) 


Thanks are given with kudos and marking the solution to a post when applicable.

0 Kudos
Message 5 of 5
(5,848 Views)