Products > Test Equipment
Free HP3478A multimeter control program.
coromonadalix:
the usb gpib adapter is now an rev 4 from galvant industries
http://www.galvant.ca/#!/store/gpibusb
and the github infos FW etc ...
https://github.com/Galvant/gpibusb-firmware
lmester:
--- Quote from: Miti on January 19, 2019, 10:56:18 pm ---Hi lmester,
I just tested this software with the USB to GPIB adapter made by Steven Casagrande, link below and, as expected, it doesn't work. How hard would it be to add this adapter to the list?
https://hackaday.com/2014/05/09/gpib-to-usb-with-a-python-api/
Edit: Never mind, it works. Thanks a lot ! :-+
Edit1: For some reason, even though I can see the readings from the instrument and (sometimes) I can control it, the message is "Instrument comm fail. Check GPIB port setting". It also cannot read calibration. Could it be because the GPIB adapter requires 460800 baud rate? In the "Default settings" it doesn't accept it but if I set it by hand in the config file, it doesn't complain.
--- End quote ---
Miti,
I've uploaded a new version of the program. It now allows higher baud rates. This was a bug in my baud rate range check. Editing the config file to update the baud rate should not cause problems. That baud rate is valid. My range check just didn't allow it. There are no range checks for data loaded from the config file.
Since you know how to edit the config file, there are two more "hidden" settings that you can select.
Set line 20 to 1 to turn on debug messages. You could copy the contents of the Instrument status window and send it to me.
More important, some Prologix clones require a delay between commands.
Line 27 sets this delay. The default is 0. The units are milliseconds. Try 100 - 500. Very large values can effectively "hang" the program. It's actually running, but, all of those time delays add up to the point where nothing is happening.
Here is a link to the config file settings: https://mesterhome.com/gpibsw/hp3478a/Software/ConfigFile.txt
Miti:
Thanks lmester!
The baud rate works but comm still fails with delays up to 500ms. See attached.
lmester:
--- Quote from: Miti on January 20, 2019, 03:21:28 pm ---Thanks lmester!
The baud rate works but comm still fails with delays up to 500ms. See attached.
--- End quote ---
Miti,
Instrument detection is failing. I don't have your Prologix clone adapter available for testing. Debugging this could require many messages and file transfers between us to resolve the problem. We should switch this conversation to private messages or email. No need to fill up this thread with messages that would be of no interest to most readers.
I'll send you a PM.
steve1515:
Hi lmester.
I just got the same adapter that Miti has and am also having issues. It seems to not be able to read the result of the "S" command even though I can when I use a terminal program. Were you ever able to figure this out?
Here's my debug log... Any tips?
--- Code: ---Version 03/23/19
Windows 7 / S-2008 R2 Service Pack 1 Platform ID 2
Config file loaded.
Debug ON.
Command delay = 500ms.
Max COM port = 64.
OC:Open COM5 CheckCom.
CheckCom start COM5
CheckCom end CreateFileA COM5
CheckCom port found
CheckCom end CloseHandle COM5
OC:Open COM5 open port.
OC:Open COM5 OK.
CA:Start CheckAdapter on COM5
CA:Check Prologix GPIB adapter. ProVer =:"Version 5.0"
CA:Found Prologix adapter (No arduino delay).
CA:Exit checkAdapter on COM5
COM port set to COM5
IG:Start InitGPIB
IG:Find Prologix GPIB adapter.
IG:ProVer srch:"Version 5.0"
IG:Found Prologix adapter.
IG:set ++mode 1.
IG:set eot_enable 0.
IG:set read timeout:++read_tmo_ms 3000
IG:SetGPIB Address ++addr 18 success.
IG:set EOI 0.
IG:set EOS 0.
IG:Set auto talk mode off: ++auto 0 success.
IGT:QSB result
IGT:Failed instrument ID: BR$=:""
IGT LEN BR$:0
Instrument comm fail!
Check GPIB port setting!
Check GPIB port setting!
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version