viFindRsrc with USBTMC devices fails w/64-bit apps

[Makoto]

As for VISA 5, every USBTMC device must be hosted by IVI Foundation's class driver. Take a look into Device Manager to check if the device is hosted by "ausbtmc.sys" placed in Windows/System32/Drivers directory. The latest driver version is "File version = 79.05.13322.00" No other drivers are considered as USBTMC host.

[lecroyDev]

Yes, this is indeed the case, path, name, and version match.

[Rikud · Accepted solution]

If you look at the release notes for NI-VISA 5.1.1 you will find this tidbit:

310315

Both viFindRsrc and the VISA I/O Control do not list USBTMC devices in 64-bit applications Calling viFindRsrc in a 64-bit application or expanding the VISA I/O Control in 64-bit LabVIEW will not return USBTMC devices. VISA is still able to correctly open a session and communicate with the USBTMC device through other functions. Workaround: For the I/O Control, provide the USBTMC device with an Alias through MAX and change the filter on the I/O Control to show "All defined aliases for resources of this class" to allow the device to show up. There is no workaround for viFindRsrc. Reported Version: 5.1    Resolved Version: 5.1.1    Added: 08/09/2011

[lecroyDev]

Superb, many thanks for posting this, comforting to know hat I wasn't imagining it 🙂

[deryoshi]

---

@Makoto wrote:

As for VISA 5, every USBTMC device must be hosted by IVI Foundation's class driver. Take a look into Device Manager to check if the device is hosted by "ausbtmc.sys" placed in Windows/System32/Drivers directory. The latest driver version is "File version = 79.05.13322.00" No other drivers are considered as USBTMC host.

---

When i got exactly this driver installed on my System, should i see the device(Rigol Multimeter)in MAX ? Or do i still need the driver wizard? Im asking because im trying to get my Rigol DMM 3062 via USB to Labview 11 and VISA 5.1.1 on a x86 Win7 machine.

[deryoshi]

Sorry for this double posting but i were not able to figure out how to edit twice.

Ich read about a niusbtmc.sys which was called the tmc driver from NI. Here we have on ausbtmc.sys which was assigned to agilents visa driver.

(old thread)

Is this outdated or do i still need niusbtmc.sys for NI-MAX?

[Makoto]

I dont know if Rigol 3062 USB is USBTMC compliant or not. If USBTMC compliant, you have no additional steps to do for connecting it with VISA. The latest VISA versions (of VISA SPEC 5.x), the default device driver ausbtmc.sys installed together with VISA Shared Component will host the device and VISA automatically recognizes the device.

You should contact the manufacturer if the device is USBTMC compliant.

[Makoto]

niusbtmc.sys is the USBTMC driver installed from NI-VISA 3.x and it is too old. asubtmc.sys is originally from Agilent IO libraries but now latest VISA versions all rely on asubtmc.sys which is installed with VISA Shared Component.

You should uninstakk all VISA libraries then install a new one.

[deryoshi]

Thanks for your both answers.

Manufacturer says its USBTMC. With their Software the DMM works fine on PC, but its not that bulky. Maybe firmware problem? I contacted Rigol support two weeks before but there is only one answer a day because of the different time zones USA/Germany. Also im not feeling that comfortable with their support. 

Best regards,

deryoshi 🙂

[Makoto]

Go Device Manager and open the device's property, then try uninstall the device driver once. After that re-connect the device USB cable again. If something is going wrong regarding the driver installation, re-installing the driver may fix the issue.