No supported device found (for USB-to-USB oscilloscope)

[Dennis_Knutson]

It seems MAX sees the scope.

[smercurio_fc]

Your USB connection clearly indicates it's being recognized as a RAW device. As Dennis pointed out, you could easily use VISA if the device supported the USBTMC spec. It does not seem to, so unless you want to spend the next few months learning about USB low-level communication, check with Yokogawa to see if they have a driver to perform communication over USB. If they do it will come in the form of a DLL or an ActiveX library. Your other option is to switch to a serial or GPIB connection. Then you can use the drivers that are available here on IDNET.

[soongwm]

Thanks guys 🙂

I guess serial/GBIP is my only option as I need a quick solution for urgent need. 

[Dennis_Knutson]

It pays to read some of the files. If you downloaded the driver from here, you would have seen the ykdl_USB.inf file and in that file, it says it was developed with the NI-VISA Development Wizard. If you used that inf file as part of the installation, it would appear as a VISA resource and you could use the driver for a USB connection.

[soongwm]

Dear all,

I installed the instrument driver before posting this thread. And it led me to seeing the USB device as RAW.

I have changed the connection to serial-to-serial (one of which has got a male-to-female converter). However, MAX window and NI-DAQmx do not show up supported device.

So are am I back to the starting point to develop my own input/output for the oscilloscope?

Thanks. 

[Dennis_Knutson]

Some clarification is necessary. You downloaded a LabVIEW instrument driver and a windows driver (.inf) in the zip file. The LabVIEW driver has nothing to do with what is or is not seen in MAX. For that, the windows driver should be what is placed in the appropriate windows folder or it should be what you pointed to when you first plugged the usb cable from the instrument to the pc. When windows prompted for a driver, this is what you must specify. You can check in windows device manager to see what driver the os is using. If you have problems with the usb connection, you should contact the vendor.

If you decide to use a serial connection, then MAX will not show any device that you have connected. It will only show your com port.

DAQmx has nothing at all to do with the scope and this has already been mentioned.

[soongwm]

Hi guys,

After reading through the files, I finally realised the whole concept about MAX and NI-DAQmx. I didn't know DAQmx was actually the NI hardware. Thanks for pointing out.

Currently, I am resorting to Serial-to-serial connection and I managed to send *IDN? command and parsed the source.

The instrument driver only provides TCP/IP input for the example. Do you think it is all right for me to replace the TCP/IP input with a Serial I/O VISA without changing much of the block diagram?

Thanks. 

[Dennis_Knutson]

Don't know what you mean since the driver supports GPIB, Serial, and USB.

In any case, there is no such thing as TCP/IP VISA or Serial VISA. There is just VISA. The only difference is that a program that supports serial will have a control to set the com parameters and serial often requires a termination character. A single driver will often handle all 4 protocols. Just look at the shiping 34401 driver.