GPIB Initialization problems

[Javier Pena]

Hi,

I'm using LabView 6i with a Fluke 45 IEEE dmm. The communication works fine as long as I use MAX to initialize the GPIB. I tried the GPIB Initialization function and it does set the meter in REMOTE, but that's it. It doesn't allow me to send any command. In order to do it, I have to go to MAX. I'm using the regular write and read GPIB commands. Any suggestions?

Thanks in advance,

Javier Pena

[CraigGraham]

Problem is often in message termination- you send a command to the
instrument butthe instrument doesn;t start processing it until it receives
the termination signal. If you get this wrong, communication appears to
hang.

You need to read the DMM manual and see what termination is required. Or try
adding CR, LF, or CR-LF to the end of your string.

"Javier Pena" wrote in message
news:50650000000800000015360000-1007855737000@exchange.ni.com...
> Hi,
>
> I'm using LabView 6i with a Fluke 45 IEEE dmm. The communication works
> fine as long as I use MAX to initialize the GPIB. I tried the GPIB
> Initialization function and it does set the meter in REMOTE, but
> that's it. It doesn't allow me to send any command. In order to do it,
> I have to go to
MAX. I'm using the regular write and read GPIB
> commands. Any suggestions?
>
> Thanks in advance,
>
> Javier Pena

[Javier Pena]

Thanks for your input Craig,

The GPIB commands in LabView work fine, I can read and write without problems, but only once the meter is initialized (or detected/configured) in MAX, and that would work only while the computer is on. My question is if there's any difference between the GPIB initialization function and the process MAX uses to initialize the device. I have the GPIB initialization function at the beginning of the program. I've tried different combination of parameters and it does set the meter in REMOTE mode, but when I send the next command (let's say... VAC) it doesn't work. So I go to MAX, send an *IDN? or whatever and after that, all commands from LabView work. Pretty weird, huh? (maybe not so weird for many of you, but I'm a newbie in
GPIB 🙂

Thanks

[CraigGraham]

Exactly how are you doing the initialisation in your code? Are you sending
*IDN? and not reading back the response by any chance?

"Javier Pena" wrote in message
news:5065000000050000003B550000-1007855737000@exchange.ni.com...

> does set the meter in REMOTE mode, but when I send the next command
> (let's say... VAC) it doesn't work. So I go to MAX, send an *IDN? or
> whatever and after that, all commands from LabView work. Pretty weird,
> huh? (maybe not so weird for many of you, but I'm a newbie in GPIB 🙂
>
> Thanks

[Javier Pena]

I have a sequence structure. The first frame contains the GPIB initialization function, which only has the address the meter is at (1) as the only parameter, then, on the next frame, I send a command using the write function (here I use the VAC or MEAS?), then, on the frame after that, I use the read command to get the reading (in the MEAS? case). On all functions (including the Initialization), I only use the address parameter, which is 1 (the address the meter is at). Any suggestions?

[LQ]

Try putting the read function on the same frame. You can also try putting
GPIB Clear function before GPIB Send.

Nam.

Javier Pena wrote in message
news:50650000000500000047550000-1007855737000@exchange.ni.com...
> I have a sequence structure. The first frame contains the GPIB
> initialization function, which only has the address the meter is at
> (1) as the only parameter, then, on the next frame, I send a command
> using the write function (here I use the VAC or MEAS?), then, on the
> frame after that, I use the read command to get the reading (in the
> MEAS? case). On all functions (including the Initialization), I only
> use the address parameter, which is 1 (the address the meter is at).
> Any suggestions?

[LQ]

Without using MAX, try to retart your instrument (i.e. DMM) after your
program is running. Other than CR or CR+LF, ; (semi colon) could be used for
command termination.

Good luck,

Nam.

Javier Pena wrote in message
news:5065000000050000003B550000-1007855737000@exchange.ni.com...
> Thanks for your input Craig,
>
> The GPIB commands in LabView work fine, I can read and write without
> problems, but only once the meter is initialized (or
> detected/configured) in MAX, and that would work only while the
> computer is on. My question is if there's any difference between the
> GPIB initialization function and the process MAX uses to initialize
> the device. I have the GPIB initialization function at the beginning
> of the program. I've tried dif
ferent combination of parameters and it
> does set the meter in REMOTE mode, but when I send the next command
> (let's say... VAC) it doesn't work. So I go to MAX, send an *IDN? or
> whatever and after that, all commands from LabView work. Pretty weird,
> huh? (maybe not so weird for many of you, but I'm a newbie in GPIB 🙂
>
> Thanks

[Rob Cole]

Do you get an error when sending? Or does nothing happen? You might try using the NI Spy program to watch the GPIB and see what (if anything) is being sent on the line. You may have to add an EOL (CR/LF combination) to the end of the command that you are sending.

Rob

[Javier Pena]

Thanks so much for your response Rob,

I don't have problems communicating with the device via LabView once it is initialized using MAX. What I've been wondering is if there's any difference between the GPIB Initialization function and the procedure MAX uses to initialize the device. I've tried the function using different combination of parameters with no avail (I have the initialization function in the beginning of the program). Once I run MAX the device would work while the computer is on, but when I shut it off, it doesn't start by itself with the function in the program, so I have to open MAX, send an *IDN? and bingo!!, now I'm able to send and receive information with the write and read functions directly from LabView. That's something I can't do
with the initialization function alone. Weird, huh?

[belfast]

I have the same problem here... i found out it was because .. MAX actually did initialize the GPIB interface when u scan instruemtns.. Meanwhile, if u run ya program in LABVIEW. Eg: communicating with non-HP instrument, GPIB initialization is required!!!