NI's VISA32.DLL not compatible with Keysight's

[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.

[pwjddl1126]

Hi, member

Did you check out the following documents? You can check what you have to do in 'LabVIEW' part of the document.

Please refer to the doucment : https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9t6SAC&l=en-US

LabVIEW 
Uninstall NI-VISA, and install HP-VISA. Use the VISA functions in LabVIEW to access the HPIB board.

By default, a VISA resource name constant or control will only allow devices defined in Measurement & Automation Explorer (MAX). Since HPIB boards using HP-VISA will not be found by MAX, you must right-click on the control or constant and select "Allow Undefined Names." This will allow you to manually enter the address of the instrument. Then, you must get the proper board and instrument address from the Keysight I/O configuration utility. Once you have that information, type the resource name according to the standard convention GPIBx::y::INSTR, where x is the board index number (usually 0) and y is the primary address of the instrument.

[xiaochouyu]

Thank you for your reply. Very useful