LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

*IDN? works in VISA test panel but VI does not


@ben64 wrote:

Have you tried using VISA Open before the VISA Write?

 

Ben64


Yes and it returns the same error on the VISA Write.

 

But the VISA Open does not return an error.

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 11 of 13
(1,416 Views)

 


I can see a couple differences, the main one being the VISA test panel DOES NOT USE VISA?

1-viWrite and 2-viRead are the VISA test panel, 4-VISA Write my VI and that is where the error occurs. 

 

viWrite and viWrite are the C syntax call of VISA Write and VISA Read

 

There is a couple subtle differences 

1.  viWrite (TCPIP0::LCRY0614N49625::... (0x028B4920), "*IDN?.", 6, 6)
3. viParseRsrc (0x12B19590, "TCPIP0::LCRY061...5::inst0::INSTR", 6, 0)

4. VISA Write ("TCPIP0::LCRY061...5::inst0::INSTR", "*IDN?.")

 

I still don't know what to make of this.


1. viWrite, the first 6 is the number of bytes to be written, the second 6 is the number of bytes transferred

3. The first 6 is the interface type (6: TCPIP) and the 0 is the id of the instrument connected to the interface: inst0

 

Now, I can't see why you are getting the error. I don't think it is necessary to concatenate \n after *IDN? but it should'nt cause any error adding it.

 

Ben64

0 Kudos
Message 12 of 13
(1,398 Views)

I can get it to work if I install LeCroy's "VICP Passort" and place the scope remote control in VICP mode instead of LXI.

 

I am guessing this instrument was never really LXI compatible.

 

This becomes a real P.I.T.A. for me now because it meant I have to install VICP on all the various target machines. And I have to train people on how to set it up and use it because using VICP the scope does not not show up in NI-MAX like it did in LXI mode.

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 13 of 13
(1,376 Views)