NI-Device 1.01 and NI-VXI 3.2 appear to be incompatible. Is there a solution or work-around?
This incompatibility manifests itself as a failure of the CGpibDevice::Initialize() function with error NIDEVICE_ERROR_INSUFFICIENT_MEMORY if NI-VXI 3.2 is installed on the system. The same call completes successfully when NI-VXI/VISA 2.05 is present instead.
My application needs to:
- Configure the GPIB interface to multiple simultaneous GPIB addresses, hence the use of version 1.01 of NI-Device.
- Perform block moves to and from a register-based VXI instrument without the occassional 'excessive PCI retry' (reported as 'access width not supported') errors that I was seeing with NI-VXI 2.05, hence the use of NI-V
XI 3.2.
Though I'm using HLA calls from the NI-VISA API to access the VXI instrument, I assume that the PCI retry errors that I was getting from NI-VXI 2.05 originate at the VXI driver level, so switching to either LLA fns, or the NI-VXI API (and sticking with version 2.05 of NI-VXI) wouldn't help me. Is this assumption correct?
(I like the way NI-VXI 3.2 has knocked 95% off the duration of my viMoveOut16() calls, so a solution which allows me to keep NI-VXI 3.2 would be much appreciated!)