Agilent 82350 PCI GPIB timeout

[albertpiero]

Hi, I am now using the Agilent 82350 PCI GPIB card to control a Klinger CC1.1 step motor controller.

I have used the Agilent I/O Configuration utility downloaded from the Agilent website.

Although the computer can detect the CC1.1 step motor control with auto detecting its address, I can't control the motor by my Labview program.

Then, I tried to send the commands using that agilent I/O configuration utility. But it fails. The utility returned a timeout error VI_ERROR_TM0.

So, is that the problem from Klinger CC1.1 step motor controller?

[f.grasdepot@laposte.net]

Hi,

1) Are you sure it is possible to control a 82350 PCI GPIB board from
LabVIEW ? Please tell me how, I am interested ...
I thought it was only possible ( at bus level ) with the NI boards
and possible with some incompatibilities at VISA layer level with board
of other manufacturers ...


2) To solve your problem, you might do the following:

- verify that your Agilent board driver has been installed ( for
instance re-install it , I mean SICL32, VISA etc ... )

- install a free gpib software to make a check with an independent
program ( www.labtab.com is an example )

- find an Agilent voltmeter AG 34401A and replace your Klinger with it
to eliminate Klinger-related problems

- send an idn? string with both labview and labtab toolbar direct
dialog and wait for an answer of the voltmeter

When one of the software works, make sure of your klinger address and
send a string command to your klinger. Pay especially attention to add
terminators ( rc lf etc ... needed ) and make sure the EOI signal is
understood and sent by the 82350 ...

The allmighty GPIB genius should spread out of the lamp at some time
and stay with you definitely ...

The Klinger documentation may help ...

If you can give access to your instrument on the Internet (public IP )
, I or some Klinger specialist can also program your Klinger remotely (
labview or labtab ) ...
You can so ask the manufacturer of the Klinger to help you

Regards,

FG

[Anonymous]

albertpiero wrote:
> Hi, I am now using the Agilent 82350 PCI GPIB card to control a Klinger CC1.1 step motor controller.
>  
> I have used the Agilent I/O Configuration utility downloaded from the Agilent website.
>  
> Although the computer can detect the CC1.1 step motor control with auto detecting its address, I can't control the motor by my Labview program.
> Then, I tried to send the commands using that agilent I/O configuration utility. But it fails. The utility returned a timeout error VI_ERROR_TM0.
>  
> So, is that the problem from Klinger CC1.1 step motor controller?

If the timeout error occurs during reading from the instrument you
might try adding a linefeed character (ASCII code 10, '\n') to the end
of each string you write to the instrument. For reading, set the
VI_ATTR_TERMCHAR property to 10 and turn on the VI_ATTR_TERMCHAR_EN
property so that reading will terminate when the linefeed character is
received from the instrument. Some older GPIB instruments do not
respect the EOI (End-of-input) GPIB bus signal and instead rely on the
linefeed character. You can set these properties from the older "Visa
Assistant" I/O communication utility that ship with Agilent's I/O
Libraries.

If you can't even open an I/O session to the instrument you are either
using the wrong address or either the instrument or the card isn't
working. You can eliminate the card as the culprit by hooking it to a
different GPIB device such as an instrument and attempting to
communicate with it.

Good Luck!


Dave Gladfelter

[albertpiero]

FG,

In fact, I am not using Labview to control 82350 PCI GPIB board. Instead, I am using Labview to control the Klinger CC1.1 step motor controller through 82350 PCI GPIB board for data transfer.

And I have tried sending a idn? string to the klinger step motor controller by the Agilent I/O Configuration utility before. But it only returned an error message.

Anyway, thanks for your advice and I will try it later today.

Regards,

Albert

[albertpiero]

Dave Gladfelter,

Thanks for your advice. Maybe that is the problem~~!

Let me try it first.

Regards,

Albert

[albertpiero]

Dave Gladfelter,

I have tried all the method mentioned but it is still failed.

I have also tried to replace the klinger controller with Agilent Voltmeter as FG said. It successes to control it.

But when I change back to klinger, the timeout message bounce out again.

So, is there any other solutions?

Regards,

Albert

[Ebele_Obijiofor]

Hi Albert,

It seems the problem is with the Klinger step motor since you only see the timeouts with it. Verify that you are sending the right commands and termination characters. I am sorry there's not much else I can do to help out. You might have to contact the manufacturer to see if they can help. Thanks!