LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Instrument Control HP 5062A Via GPIB

Hi ,

   

         Im having problem with markers , when i set it on signal , its ok , but when i query the Yaxis of markers , a query interrupt the other . I tried delay with serveral values , but didnt work . PS : When i read only 1 mark , its work , but im using a for loop , to take all 9 markers automatic . 

I think that i m using the right SCPI command .... :CALC[ i+1 ]:MARK[ i+1 ]:Y?           [ i ] = NUMBER OF ITERATIONS OF FOR LOOP (BEGIN ON ZERO, THEN I ADDED +1 )   

 

Thx 😃  

0 Kudos
Message 1 of 10
(3,413 Views)
Try using the drivers already written for that instrument.
0 Kudos
Message 2 of 10
(3,409 Views)

Another problem , im using labview 6.0 and i cant upgrade cuz must pay to do it =\ ...

 

0 Kudos
Message 3 of 10
(3,403 Views)
Why don't you post the actual code? What you describe is the syntax for the VISA Write. Are you doing a VISA Read immediately after? A query interupted is just what it sounds like. You send out a query (a command with a '?') and another query is sent when there is still data in the buffer that has not been read.
0 Kudos
Message 4 of 10
(3,394 Views)

Yes !  ... Im using Visa write , and a sequence structure , after the Visa Read ... i put a delay between both .... And this error occur ... What should i do to work ?

Thx 😃

0 Kudos
Message 5 of 10
(3,365 Views)
You really need to post your code. Just use the 'Add Attachments' right below the message body. At the very least, attach an image of the block diagram though the actual VI would be better.
0 Kudos
Message 6 of 10
(3,352 Views)

Hi ,

 Here , im adding the code and the image of it .... Has a delay between the wirte and read ... i didnt added on image this part ...

Thx for the help 😃 

Download All
0 Kudos
Message 7 of 10
(3,326 Views)

Those are not VISA functions. Those are old-style GPIB functions. You have the following problems:

 

  • According to the drivers that are on the NI site, the write command needs to be terminated with a linefeed character. Thus, you need to append a linefeed to your command string.
  • You are not setting the number of bytes to read for the GPIB Read. Use a large number, like 512. The read should end automatically.
  • You do not have any of the error clusters wired, thus you will never know what error, if any occurred.
0 Kudos
Message 8 of 10
(3,322 Views)

But when i use the mode 1 in the write component , the help menu says that append CR to the string and send EOI with CR.

 

 

And the read >>>>   mode specifies conditions other than reaching byte count for terminating the read.

0    No EOS character. The EOS termination mode is disabled.
1    EOS character is CR. Read terminated on EOI, byte count, or CR.
2    EOS character is LF. Read terminated on EOI, byte count, or LF.

 

 

0 Kudos
Message 9 of 10
(3,316 Views)
A linefeed and a carriage return are two different characters. If anything, you should be using mode 2, not 1 on the Write, if you insist on using the old GPIB functions. As for the GPIB Read, I do not know which mode is appropriate for this instrument - you need to check the instrument's manual.
0 Kudos
Message 10 of 10
(3,310 Views)