I have version 3.1 of the communications manager which works fine with an application that is written which uses the old NI-FBUS API (the C functions). On a different appliction which is coded up in a new application which uses the new NI-API (.NET code) the FBUS communications manager 3.1 crashes. I have an AT FBUS card and wonder if that is a source of the problem. That being that verions 3.1 of the FBUS Communications manager it is not compatible with an AT card. I thought someone told me they "figured out a way" to get the communications manager version 3.1 to work on the old AT card??? So question #1 is an AT card compatbile with FBUS communication manager 3.1?
When FBUS communications manager crashes it is very random and doesn't seem tied to a device under test. It happens sometime when doing reads, sometimes when doing write....there does not seem to be a specific point or location that it fails. Again some times it runs fine for a long time and then fails other times it fails almost right away. I have to restart the communications manager to get it to work again and reconnect a device. Again my old program that uses the old NI FBUS API works great on the same card with FBUS Communications manager 3.1.
