I've been having problems with the USB-VXI drivers. The cause can be different, but the symptom is always the same.
Symptom: The computer hangs inside a VXIMove. There is no way on the computer end to recover once you are there (killing LabView takes a while, with a "Resetting vi" message, and then the computer won't even reboot without a hard reset). I did find that cycling power on the VXI chassis does get out of the lockup situation. But in any case, it's not a stable environment.
I have seen this happen at times on a straight USB connection, but the big problem system is admittedly more complex. It uses USB-to-fiber transceivers so that the VXI chassis can be 50 meters away from the control computer (tried the fiber-VXI connection and had a multitude of problems; inconvenient power-on sequence restrictions, problems passing fiber through bulkheads, etc.). Anyway, in this form, it may work fine for a while, but seems to hang when the rate of VXI traffic increases. This is an application that has run for years using MXI-2 connections.
On another (straight-thru) system, I've seen the identical problem simply when another near-by device was powered on during times of heavy VXI access (power was properly conditioned; this problem is more rare but still happens).
Of course, these systems are using the only form of NIVXI drivers that supports USB (3.5).
So my questions are: any thoughts? Will an updated version of NIVXI in the near future likely resolve the problem?
Note: on the key problem system, we originally used USB-1.0 to fiber transceivers. These gave no problems, but VXI operations took way too long...
Never had any problems with MXI-2, but it's not suitable for this one version of our system...