Google Ad

Project 025 - WinGPIB - GPIB Windows Software

DISCLAIMER: This video is educational only, so if you decide to do the same yourself then you are on your own, I can't be held responsible for any problems/issues/damage/injury that may occur if you decide to follow this blog and try it yourself.


WinGPIB App rebranded 2nd Jan. 2022 - UK/USA Trademark.

This app provides reliable Windows GPIB functionality to many brands and types of test instruments.

Written in Visual Studio 2019 VB 2022 VB and using Pawel Wzietek's awesome GPIB library code (.DLL Multi-threaded GPIB communication), I wrote a custom front end to what you see below.
The app can interface using VISA, GBIP:ADlink, GPIB-488 and COM port......and can run two devices at the same time.
Pawel's original project:

99% of instruments with a GPIB inteface will work with this app because it is extremely flexible.
- GBIP:ADlink
- GPIB-488
- COM port

The app primarily works with Keysight IO Libraries and using the Agilent E5810A or the Agilent 82357B etc. Not to say it won't work with other interfaces, your mileage may vary.

USB-TnH SHT10 V2.00 & USB-TnH SHT30 (Usb serial comms)

Win11 - reports in so far that it is ok with Win11.

Go HERE to download and to get the latest information (EEVBlog forum).
[all files are scanned with BitDefender Antivirus prior to upload]

First, make sure you have the Keysight IO Libraries loaded, running and configured. Then,
- Unzip
- Run WinGPIB.msi file.
- A desktop shortcut is created to run the app.
- All user data resides in C:\Users\[username]\Documents\WinGPIBdata

Possible VISA32.DLL Issues:
If you have Keysight IO Libraries loaded and you can communicate with your device using it's GPIB address via the Connection Expert but get an error (Visa error BFFF009E) using WinGPIB and you've tried everything, then:
Go to C:\Windows\SysWOW64
Rename Visa32.dll to Visa32_old.dll
Rename visa32.Agilent Technologies - Keysight Technologies.dll to Visa32.dll
Reason: Windows updates and updates to other programs on your PC can often replace this .DLL with their own and breaks WinGPIB Visa functionality!

Installation Notes:
1. To update the app use Windows ADD/REMOVE PROGRAMS. When you uninstall, the Data folder will remain intact with any new files you've created in there, but GPIBchannels.txt and Log.csv files will be back them up first if you've customized them.
2. The program is installed at: C:\Program Files (x86)\WinGPIB
3. If you accidentally delete your GPIBchannels.txt or base Log.csv file there are copies in the program folder you can copy out.
4. When upgrading you may lose the contents of your profiles. Take screenshots or make notes.
5. WinGPIB does not use OneDrive for it's data storage.

Moving your device settings etc to a new PC:
On your old PC (I'm using Win10) go to:
and in there is a file called user.config
Copy that file out and put it in the similarly named folder in your new PC. The large folder name will be different.
Note: The main EXE is now called WinGPIB.exe from 13/06/23

This app is freeware. It must not be used for commercial purposes.
Please contact me privately for a copy of the source's too big to attach to this forum now.
- Unzip the folder.
- Open the .vbproj in VS (folders will be created).
- From the installation zip file (separate download), copy files IODevice.dll & Microsoft.VisualBasic.PowerPacks.dll, Log.csv & GPIBchannels.txt to the new /bin/debug folder.

Assumes that you have loaded the current version of Keysight IO Libraries Suite and have it configured.

Set up your NAME and ADDRESS of the device(s) you want to connect to, and pick the INTERFACE type (I have tested Visa only).
The defaults shown when you install are my own as an example.
Hit the CREATE DEVICE button (you choose). An pop-up box will appear that lists the connected device. This box will remain visible at all times and will let you see the commands being sent and any queued commands.

You can effectively batch commands using the PRE RUN, AT RUN and AT STOP boxes and using the RUN/STOP button at the bottom.
PRE RUN commandsare used to set up your device.
AT RUN command is the command that is repeated at the SAMPLE RATE.

Command types are as follows:

Enter single commands in the COMMAND boxes and hit QUERY and you'll get a RESPONSE back.
Types of commands as follows:-
Query Blocking commands are immediately executed/sent. They are immediately executed on the calling thread (usually GUI thread), this method waits until it gets response from the interface.
Query Async commands are queued. Queries are queued and the queue is processed on a different thread (producer-consumer model). The call appends the query to the queue and returns immediately.
Send Async  commands queued. These types of commands do NOT expect a reply.

PRE RUN - Initialize your device with a list of SEND ASYNC type commands.
AT RUN - A single QUERY ASYNC type command.
AT STOP - A list of SEND ASYNC type commands you may wish to send when you hit STOP.

You can specify an Async (no reply) command to be send periodically, such as ACAL DCV when you are logging etc.
Duration in secs = How long you need that command to be active for, i.e. ACAL DCV on a 3458 may take 60secs.
Period in mins = How often do you want that command sent, i.e. every 120mins.

When the CREATE DEVICE buttons are pressed a pop-up box will appear that lists the connected device(s).
This box will remain visible at all times and will let you see the commands being sent and any queued commands.
Note that you can close this window without any effect on the app. You can use the button "Show Device List" to show it again if needed.

After connecting to your device(s) use the comand line interface to send and receive data from your device(s).

There is only a couple of Temperature/Humidity sensor I have tested and that are available from DOGRATIAN seller here:-
They are serial USB type sensor and does not require any drivers except what Win7/Win10 loads automatically as you insert it. You should see a COM port which you can pick from the list on the app.
The SHT30 gives 2dp's whereas the SHT10 1dp.

For CSV generation, per the defaults, set up your filename and path to where you want the CSV to be saved. At the moment there is not file generated if it doesn't exist so make sure you have an empty .CSV text file at the path specified.
The check box ENABLE CSV will start saving data to the .CSV file.
The EXPORT CSV file will copy the active .CSV file to the same folder and append the current date & time as the filename.
EXPLORER will launch Windows Explorer and pointing to the path folder.
You can clear the current CSV file with the RESET CSV button, there's a check box next to it which must be set before the reset will work.
ENABLE LOG check box will activate the log file display window.
E NOTATION TO DECIMAL check box will convert ########E-02 to the decimal equivalent. This is for the CSV and well as the log window.

Enable either or both device charts via the check boxes.
With the boxes un-checked you can hit the CLEAR CHART to reset the chart windows and remove the data.
You can change the resolution of the chart with the X-AXIS SCALE POINTS entry. Once the chart display reaches the set number of data points on it the chart will start to scroll off to the left as new data appears at the right.
The range of the Y-axis is adjustable via the SCALE MIN AND SCALE MAX enries. You can manually set them or hit AUTO SCALE and the chart will look at the existing trace and from it's highest and lowest position will centre and scale the chart.
The UP and DN buttons allow the current set scale to be adjusted in 10% steps.

For offline display of the generated .CSV files. The user can select the Device to be displayed on the graph (since there are 2 devices available), and also zoom in/out and scroll back/forward through the graph.

3458A & 3457A DMM RAM EXTRACT:
Utility to extract the battery backed up (DS1220Y IC) cal ram on the 3458A down to a .bin file.
Utility to extract the battery backed up (DS1235Y ICs) settings ram (both) on the 3458A down to a .bin file.
Utility to extract the battery backed up cal ram (2 versions) on the 3457A down to a .bin file.

Utility to automate the full calibration (DCV & DCI) of an HP 3245A by using a 3458A.

Most of the entries are saved off so when you restart the app they will be there.

1. Power up E5810A and make sure it gets an IP assigned (DHCP), i.e.
2. Go to and "Find & Query Instruments". Make sure you can communicate with your device.
3. Go to Keysight Connection Expert and ADD Remote GPIB Interface.
    Change SICL Interface ID to the one that finds the IP of the E5810A. Hit OK.
4. Now a device will be listed on the "My Instruments" panel. The GPIB address will be displaye i.e. GPIB1::22:INSTR

CR carriage return……..moves to column zero without advancing paper
LF line feed…… advances paper without returning to column zero
CRLF……. does both the above
\r = CR = 0x0D = 13
\n = LF = 0x0A = 10 = newline


ISSUE 1: MAV not set errors:
Example: "Poll timeout: MAV not set, status byte=4"
Check your device manual to see where the MAV is coded in the status byte and set the MAV mask accordingly.
The standard value is 16 and is set by default in WinGPIB
If it still doesn't work the only option is to disable polling altogether although you then might experience
delays if you have more than one device connected via GPIB.
Also, if this is happening with large NPLC settings or other such time hungry commands then try increasing the Timeout (ms) to 10000 or 15000.

ISSUE 2: Can connect to my device but get syntax errors, no command is actioned:
I have found a dodgy GPIB cable/connector can cause this.

ISSUE3: The main WinGPIB.exe is sometimes flagged up & quarantined by Windows anti-virus scans. Three times now it's been flagged as containing a virus and three times now I have sent it in and it's been confirmed as a false positive. Twice by BitDefender, and once by Microsoft Defender. If it happens to you then please let me know and I will contact the anti-virus company involved.

Have fun.


Screenshots below (reduced in size for my webpage) - These are not the latest, I don't keep the screenshots up-to-date with each GUI mod: