I am trying to use NI-VISA through a USB-RS-232 adapter. What I atrying to do is have NI-VISA see the adapter as a COM1 and allow communication over the USB bus. Does this work? Has anyone had any success?
I beleive that is an IOGEAR. The request is coming from our end-customer. What we did is to use the NI-VISA IO Layer in some application software. The software was designed for RS-232 using NI-VISA. What I am seeing is customers getting these adapters for their laptops which only have USB support. What I will try to do is get one of these adapters and test the combination using the NI-VISA with them. Any insight we be helpful. I have been lead to beleive that the adapter and driver emulates a COM1 port. I am hoping that NI-VISA just leverages the USB-RS-232 adapter as a generic serial port.
My understanding is that VISA makes WIN32 calls, and if the serial device behaves properly, those calls will work regardless of the type (USB, built-in, etc.). VISA doesn't know anything about the type of interface being used (ethernet, RS-232, PCI, etc.) - managing those differences is the responsibility of the serial device's driver.
Can NI-VISA handle COM numbers greater than 4. For an example most PCs may have a COM1 and COM2. SOme have COM3 and COM4. If the USB-RS-232 adapter emulates to COM5, will the NI-VISA layer handle it? What is the limit? We only have had success with NI-VISA up to COM4. My thinking that some of theese adapter drivers may default to COM5 in order not to conflict with COM1-COM4. Any thoughts?
We figured it out while you were checking into the issue as well; the customer was using a a Toshiba P25 laptop with a Keithley 6485 Picoameter (serial interface), and one of the problems was that the USB-RS-232 driver was assigned to COM14(!). The customer forced the USB to Serial to be on COM3. The Toshiba is now talking to the 6485 with no problem using NI-VISA. The issue appears to be related to higher level COM#s.