NI CAN communication

[ELI2011]

Software: LabVIEW 2012

Hardware: NI 8473

OS: Windows 7 Enterprise

refer to below figure, send command to DUT using CWrite, then get response from DUT with CRead. But as DUT continue to send out mass messages while I only want the expected response with fixed arbitration ID 0x629, that is why I am using the while loop here.

My question is: do we have other ways to receive response with expected arbitration ID only, and bypass other messages automatically?

Thank you!

[Taki1999]

The 8473 is a bit special.

It claims not to support ncConfigCANObject.

I think it does work though.

You can then do a Read Object instead of a Read Multi.

From the Help on ncConfigCANObject:

ObjName is the name of the CAN Object to configure. This name uses the syntax "CANx::STDy" or "CANx::XTDy". CANx is the name of the CAN network interface that you used for the preceding ncConfigCANNet VI. STD indicates that the CAN Object uses a standard (11-bit) arbitration ID. XTD indicates that the CAN Object uses an extended (29-bit) arbitration ID. The number y specifies the actual arbitration ID of the CAN Object. The number y is decimal by default, but you also can use hexadecimal by adding "0x" to the beginning of the number. For example, "CAN0::STD25" indicates standard ID 25 decimal on CAN0, and "CAN1::XTD0x0000F652" indicates extended ID F652 hexadecimal on CAN1. The special virtual interface names "CAN256" and "CAN257" are not supported for CAN Objects. The 847x and 847x with Sync series CAN and LIN interfaces do not support ncConfigCANobj.vi.

[Hooovahh]

If the making isn't supported on this device then you are out of luck.  But it really doesn't take that much time to read a frame and throw it away if it isn't the right ID.  Of course if you could purchase the more expensive XNET hardware it has lots more capabilities with filtering conversion and a whole slew of awesome features, that you may or may not need.