Page 1 of 1

HP 6890 GPIB problems

Posted: Wed Aug 18, 2010 3:18 pm
by nk1124
I have a HP 6890 plus with firmware rev a.03.08(GPIB Address 5) connected to a Agilent 82350B PCI gpib card and a 7673A autosampler controller(GPIB Addr 8), and using Agilent IO Suites 15.5. When I hook everything up and run the connection utility the 7673A identifies itself fine immediately. The 6890 fails to return an IDN string. The program can see something is there at address 5, but when any queries are sent no responses are received. Does anyone have any ideas on how to resolve this? Im hoping its not something horrible like a blown main board.

If it makes any difference, no gasses are hooked up yet, only the communication and power cables.

Posted: Fri Aug 27, 2010 6:55 pm
by chromatographer
Try swapping address on the injector and GC. Does it still recognize the injector and not the GC? Also swap cables to check the cables.

Do you have an extra GC and PC? Then you could try swapping equipment around.

Posted: Fri Aug 27, 2010 8:33 pm
by nk1124
Actually the problem was that the adapter needs to be renamed to hp82341 instead of 82350b. Only found that out by running a working computer and the second one side by side making everything the same.

I have everything up and working now, but crawling along with the setup it seems that the autosampler is not passing an inject start signal to the computer/GC, so it will go through all of its pre-run turret dancing and syringe filling and emptying, and inject the sample into the inlet, but the GC never enters pre-run, and even if you hit pre-run manually, it never receives a signal that an injection was made. Any ideas on whats going wrong here?

Posted: Sun Aug 29, 2010 4:47 pm
by Consumer Products Guy
Actually the problem was that the adapter needs to be renamed to hp82341 instead of 82350b.
The installation instructions for the GP-IB interface details to call it hp82341 (small hp) even if its actually a 82350 card. And to set the bus address to 30 (whatever that is).

Posted: Mon Aug 30, 2010 1:52 pm
by AICMM
nk1124,

Do you have a remote cable connected? Based on your description you have a stand-alone autosampler box separate from the GC. If this is the case, there should be a remote cable connecting the box to the GC that passes the start signal.

Best regards.

Posted: Mon Aug 30, 2010 2:03 pm
by nk1124
There is a GPIB cable and a RS-232 cable connecting the 6890 and the G1512AX/7673A and both of the cables test properly for continuity. Theres another APG remote cable, but in an identical setup that APG remote is not in use so I didnt use that cable in this setup.

--Adding the APG remote cable seems to have fixed that problem as well. Thanks

Re:

Posted: Sun Jan 28, 2024 9:02 pm
by 4g63t
Actually the problem was that the adapter needs to be renamed to hp82341 instead of 82350b. Only found that out by running a working computer and the second one side by side making everything the same.

I have everything up and working now, but crawling along with the setup it seems that the autosampler is not passing an inject start signal to the computer/GC, so it will go through all of its pre-run turret dancing and syringe filling and emptying, and inject the sample into the inlet, but the GC never enters pre-run, and even if you hit pre-run manually, it never receives a signal that an injection was made. Any ideas on whats going wrong here?
How / where did you rename the adapter? I am running into the same issue on an almost identical system. Thanks!

Re: Re:

Posted: Mon Feb 05, 2024 3:05 pm
by 4g63t
Actually the problem was that the adapter needs to be renamed to hp82341 instead of 82350b. Only found that out by running a working computer and the second one side by side making everything the same.

I have everything up and working now, but crawling along with the setup it seems that the autosampler is not passing an inject start signal to the computer/GC, so it will go through all of its pre-run turret dancing and syringe filling and emptying, and inject the sample into the inlet, but the GC never enters pre-run, and even if you hit pre-run manually, it never receives a signal that an injection was made. Any ideas on whats going wrong here?
How / where did you rename the adapter? I am running into the same issue on an almost identical system. Thanks!
Found it..

"The IO Config utility is provided in IO Libraries Suite for
backward compatibility only. The supported configuration
utility for IO Libraries Suite is Connection Expert. IO
Libraries Suite installs the unsupported IO Config utility in
the installation directory (by default, C:\Program Files\
Agilent\IO Libraries Suite), as bin\iocfg32.exe."