can't connect my Hioki 7005 DC Standard to GPIB - Page 1
Forum section: electronics / testgear

author: e61_phil
author_rank: Frequent Contributor
timestamp: March 03, 2014, 11:26:03 am
content: Hello,I've tried to connect my Hioki 7005 DC Standard to GPIB with an Agilent 82367B USB to GPIB adapter. I think my GPIB setup is correct because my HP3478A is working correctly.Unfortunately, I have no manual for the Hioki. I've tried to set different addresses by the DIP switches on the back, but nothing happend. The Agilent IO Suite isn't able to find my HiokiAny ideas?Philipp

author: VK5RC
author_rank: Unknown
timestamp: March 03, 2014, 12:23:31 pm
content: I've not used Agilents IO suite but is your Hioki set as a 'device' or 'controller', when I was getting my 8561 to talk to my computer with using a Prologix adaptor and KE5FXs GPIB toolkit programs, it was very critical to get both address and device state correct.

author: macboy
author_rank: Super Contributor
timestamp: March 03, 2014, 02:46:14 pm
content: That instrument is old enough that it will not respond to the SCPI commands that the Agilent I/O suite uses to identify instruments. If you look near the GPIB connector, it may say something like "IEEE488.2" or "IEEE488.1". If it says 488.2 then you should be able to get it to respond to the *IDN? command. If it is only 488.1 (very likely given the vintage) then it won't even resond to that, but it will Acknowledge a request to listen, so at the very least, Agilent I/O Suite will know thatsomethingis there, but not what. In the Agilent I/O suite you can manually create an instrument, specifying the address. If it responds to *IDN? then you can specify that (and its response) too.Sadly, if you do not have the manual, you will likely not be able to make use of GPIB on this, since it is too old to respond to "standard" SCPI commands, and will instead have a proprietary command set.

author: e61_phil
author_rank: Frequent Contributor
timestamp: March 04, 2014, 04:38:06 pm
content: It would have been nice to step through the output and use ist to calibrate own projects.Even my HP3478A doesn't respond to *IDN?. It send its reading with every request.Ok, I will do my calibrations by hand in the futureThanks a lotPhilipp

author: edpalmer42
author_rank: Super Contributor
timestamp: March 04, 2014, 07:15:22 pm
content: Did you find this data sheet?http://www.hioki.com/file.php?t=catalog&iid=1_383Although it's in Japanese, it includes a small program listing for GPIB communications. Should give you enough clues to get started. If you can find programming info for other Hiocki equipment of similar age you might get some more clues.Edit: Actually, when I look closer at the datasheet, it looks like it includes all the info you need.Ed

author: e61_phil
author_rank: Frequent Contributor
timestamp: March 05, 2014, 01:24:37 pm
content: Do you mean it just never responds? This datasheet looks very interesting!I will test it. Thanks

author: macboy
author_rank: Super Contributor
timestamp: March 05, 2014, 01:44:52 pm
content: In addition to the small program listing, there is an explanation on the second page. The GPIB command string consists of 6 parameters (a through f), specifying function (V/A), Range, polarity, current (or voltage) limit, output (on/off), and the amplitude setting from 0 to 12000. Fortunately, everything important is in English. With that information you should have full control.

author: alex.forencich
author_rank: Frequent Contributor
timestamp: March 05, 2014, 09:49:47 pm
content: Quote from: e61_phil on March 05, 2014, 01:24:37 pmSome of the older instruments are basically 'listen only'. It can be quite annoying for debugging sometimes. In fact, in some of these devices, the entire GPIB interface is implemented in discrete logic (7400 series), necessitating the simplest possible command set. The commands are designed to be decodable by the simplest possible state machine. If there is no need to read (like in this case), then there is no need to implement it as it would require multiple additional chips. I have an old HP 436A power meter, and the GPIB interface board is all discrete logic. No processor or firmware at all in that sucker. The actual power meter reading is actually passed to the GPIB board and the display board in parallel as four parallel BCD digits (16 wires). Quite clever, IMHO.It looks like the Hioki unit is a bit more complicated, though, and hence may have more than just discrete logic. It would be very cool to see a teardown to get a good look a the GPIB interface.Let me see if I can translate what the PDF says about the programming for this unit.The 7005-01 is equipped with GP-IB. It allows you to externally control the front panel range, polarity, limit, output value, and output state.7005-01 programming codeFunctionF0 - F1 - DC VF2 - DC ARange (volts case)R0 - R1 - 10 mVR2 - 100 mVR3 - 1 VR4 - 10VR5 - 100VRange (amps case)R0 - R1 - 100 uAR2 - 1 mAR3 - 10 mAR4 - 100 mAR5 - 1APolarityP0 - +P1 - -Output Limit (volts case)L0 - 6 mAL1 - 12 mAL2 - 60 mAL3 - 120 mAOutput Limit (amps case)L0 - 6VL1 - 12VL2 - 60VL3 - 120VOutputO0 - offO1 - onSettingD00000 - D12000ExampleTo output 100 VDC on the 100 V range with a 60 mA limit, the code is shown below.F1R5P0L2O1D10000There is no problem if the sequence is changed. Also, it is fine if the components are entered one at a time.Edit: Ha, I did not realize that O and 0 next to each other give you a little afro dude. Go figure.