VISA32.DLL of NI can't support GPIB interface

[xiaochouyu]

HI:

I use the visa32.dll development tool

Declare Function viOpenDefaultRM Lib "VISA32.DLL" (ByRef sesn As Integer) As Integer

Declare Function viGetDefaultRM Lib "VISA32.DLL" Alias "#128" (ByRef sesn As Integer) As Integer

I find that if I use the "Keysight" driver. I can control the "GPIB0::20::INSTR" address of the instrument. But I use the "NI" driver. I will not be able to control the "GPIB0::20::INSTR" address of the instrument.

Why is this?

Are two visa32.dlls different?

I find the sizes of two visa32.dlls are different.

[Dhla]

Hi

I have the same problem. Did you ever find a solution for this?

[psuedonym]

Use NI VISA or Agilent/Keysight VISA. Not both.

[Dhla]

Ok, so it all happned when I updated to LabView 2019. The visa32.dll in the SysWOW64 folder updated to something that does not work with my old VB6 visa32.bas module. So is there another visa32.dll somewhere in a Keysight version?

[psuedonym]

You will have to find out how to use the Keysight VISA and not the NI VISA.

[xiaochouyu · Accepted solution]

The problem has been solved If two drivers are hidden at the same time. Then one driver uses "GPIB0" and the other uses "GPIB1"