Has anybody captured an error frame occurence with CAN driver version 2.2

Question

I was very excited about the appearance of the Comm Error Frame Type in version 2.0 of the driver. I have a Series 2 card and was working with the CAN driver version 2.2 to attempt capture error frames with an in house written tool.
Currently we have a tool from Vector that we must use to monitor our CAN system for Error Frames that occur due to a discrepancy in the ATMEL CAN core that we are using. We would like to get rid of the Vector tool and though we could because this capability appeared to be available in the NI driver.
I executed ncConfig with NC_ATTR_LOG_COMM_ERRS = NC_TRUE and the called the ncRead command to get data from the Read Queue. The tools built upon the NI CAN driver and the Vector tool seen exactly the same data, except that when the a communication attempt was turned into an error, the Vector tool indicated and Error Frame had occurred and nothing was available from the NI tool.
Has anybody captured an NC_FRMTYPE_COMM_ERR Frame with the ncRead command, and if so would you be willing to help.
Thanks.

Answer 1

biker2000 and LoganS
Thanks for all of the support on this issue, I am better understanding how the NI CAN card works.
However, the described functionality provides little to no value in how I am using the National Instruments CAN card and I have submitted a Product Suggestion through the link provided earlier in this thread. Your example describes exactly why the implemented Error reporting is not useful. Many errors have to occur before the transition to Error Passive, but you only get the last one, which may or may not reflect what the overall problem is in the system.
Also, this leads me to another problem that I am having. The transition to Error Passive and Bus Off were added in a recent version of the CAN driver. Was there ever any though to making this configurable. It is problematic for me every time I restart the system that the NI card is connected to because the NI card ends up in Bus Off. I know this is following the CAN Protocol (our physical layer has Dominant = Zero = 0 V, when the system is powered down the NI Card would see may consecutive Dominant bits) because of Rule 6, section 8 (Fault Confinement) in the Bosch CAN specification. However, the NI card in my application is being used to monitor and interact with the system, it is not part of the functioning system. When it goes to Bus Off, my test application is dead. I would rather the occurrence of errors get reported, so I can see what the problem is, and fix what is wrong with the system, but still continue to function as best possible. I use the NI card in a lab environment for testing.
Again, thanks for everything
Nathan