09-18-2014 01:44 AM
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
09-18-2014 06:43 AM
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
09-18-2014 06:53 AM
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).
09-18-2014 08:39 AM
thanks ...............solved the problem....:-)
09-18-2014 08:46 AM
swap15 wrote:
thanks ...............solved the problem....:-)
Thanks are given with kudos and marking the solution to a post when applicable.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord