08-27-2015 03:28 AM
The 30bit is NOT your device sending that. No CAN tool supports more than 29bit for a message ID.
The only reason you got a 30bit ID from the NI-CAN driver, is that the driver adds the 30th bit to the message ID.
This has been NI's implementation to let you as a programmer know that is an extended message ID (29bit) and not a normal ID (11bit). This is also used in the driver when you want to send a message with a extended message ID.
The 30th bit is not transmitted on the bus.
But again, this is only valid for NI-CAN and its driver, not a standard CAN.
The XNET driver works in the correct way, giving you a flag (boolean) that tells you if the message ID is normal or extended.
08-27-2015 03:39 AM
thank u very much, i got it!
08-27-2015 06:34 AM
Remember to mark a solution, if you problem has been fixed.
This way peolpe can see that your problem has been resolved, and what answer did help you solve the problem.