NICAN Error 0xbff62101

[YuGen]

Hello all,  

I got an error 0xbff62101 when tried to open more than 12 Can Objects with attribute NC_ATTR_COMM_TYPE set to NC_CAN_COMM_TX_RESP_ONLY (Transmit By Response Only).

The error message is: "CAN chip supports at most 12 of the following CAN Objects: Tx By Response (Std or Xtd ID), Rx Xtd ID. Solutions: Set Tx By Response attributes to false; Config all Tx Xtd before Rx Xtd; Don't use Net Intf to receive Xtd frames (CompXtd=None)."

My question: is it possible to bypass the problem without buying additional cards? I really need about 40 Arbitration ID's of such type.

Software I used:
- NI-CAN Software for Windows 2000/XP Version 2.3.2
- Measurement Studio 8.0
- VB .NET 1.1

Thanks

[Angela M]

Hello YuGen,

No, this comm type is only for 12 objects per port, thus you would need to have 2 devices with 4 ports overall.

Regards,

Angela

Applications Engineer

[YuGen]

Hello Angela,

Thanks a lot.
Are there any manuals with limitations of such sort explained? I'm just afraid to advise buying new 2-port cards and then, all of a sudden, to find the next problem.

F.e.: 0xBFF62048: "Overflow in the CAN communication chip. This error occurs when frames are received back-to-back for long periods. Solutions: Set Series 2 Filter Mode to filter out frames; Dedicate entire CAN card to receive high busload (transmit with 2nd card, receive another network with 2nd card instead and 2nd port)."

This is page 3 of 12 in the list of error codes. I dare now to read p.4 🙂

With Best Regards,
Yuri
Software Engineer

[DirkW]

Hi Yuri,

The Object limitation is historically related to the controller chip. Because the TX by response is handled on the board directly, this needs enough space to create them.

The limit was set to 12 per port and you are the first one i know who is running into this limitation.

But you are right, this should be implemented into the documentation (manual).

Lots of the error codes are historical as well and related to older Series 1 boards, which had some on board or driver memory limitations.  The current Series 2 boards don't have these limitations anymore and should be able to handle 100 % bus load. The only limit for both Series is that both Ports are sharing one CPU. Thus  whenever the Firmware is handling lots of high priority operations for one port, this could effect the other port in terms of latency and performance.

If you need to handle high performance write operations (us) or such multi object operations, think about our Compact RIO hardware platform. this platform uses  FPGA  and you can program your CAN communication directly to the FPGA code using LabVIEW. The cRIO is available as standalone ,PCI or PXI formfactor.

DirkW

[YuGen]

Thanks a lot, LittleA and DirkW.

Just FYI: we used 2 2-port cards and resolved the problem. Thanks God, no more limitations rised up.