Why is "Device and Interface" missing from MAX Config tree?

[swint144]

Yep - I grabbed the "old style" driver for V8.x.  It was just a simple unzip to the labview directory (listed above).  Nothing that I could see would tie in to MAX, and so far it hasn't connected to the scope.  The IVI driver (including its prerequisites) was installed as a long-shot.

[swint144]

Still no solution... MAX doesn't know what devices are out there, even though it sees the VISA and LabVIEW software.  Reinstall, repair, deleting the MAX "Data" directory and having MAX rebuild the tree...  I've put in a request for a demo CD - maybe that will set MAX up correctly.  Thanks for your help, I'll post back with further results.

[alanjb]

Hi Swint,

The driver will work independent of MAX; there is no need to configure the scope in MAX at all.  In the example VIs, enter VICP::<ip address> for the resource string when configuring scope to use the TCP/IP interface.  What happens when you do this?  Do you get an error?

(Unless the MAX issue is a NI-VISA issue................. ) 

Cheers,

Alan

[swint144]

Hmm...  I was actually trying to use the LXI interface, rather than the VICP.  Looking on the scope's web server, I copied the address "TCPIP0::193.195.1.2" and put it in as the VISA resource name in Labview.  I get a beep from the scope (the sound of scientific progress) and then

"Error -1074000000 occurred at an unidentified location"

"Possible reason(s):
 LCWAVE Error Query;
instrument reports:
Unresolved parsing error."

(Wow!  An error box from which I can actually cut'n'paste the message!  Thanks NI!)

I'll try setting up the scope to use VCIP.  

[swint144]

OK, if I change to VICP, the error message changes:

"Error 85 occurred at lcwave Read Command Error.vi"

"Possible reason(s):

Scan From String (arg 1) in lcwave Read Command Error.vi->lcwave Error Query.vi->lcwave Initialize.vi->lcwave Acquire and Read MyMeasurements.vi

The format of the CMR? response is not as expected. Make sure that the Command Header is not being reprogrammed from the value configured in the Default Instrument Setup VI, where it is configured to OFF with the command CHDR OFF. (Default Instrument Setup.VI is called from Initialize.vi.)


Complete call chain:
     lcwave Read Command Error.vi
     lcwave Error Query.vi
     lcwave Initialize.vi
     lcwave Acquire and Read MyMeasurements.vi"

[swint144]

OK, the Error 85 occurred with "TCPIP0::..."  If I change the resource name to "VICP::..." AND the scope is on TCPIP(VICP) I get the Error -1074000000.

The error log on the scope shows errors from the AS Interpreter,

"error: command < VBS app.Measure.MeasureSet=0 : .app.Measure.ShowMeasure=TRUE : .app.Measure.StatsOn=TRUE : .a...Measure.HistoOn=False>  at to"

with either the VICP or the VX11 control.

[alanjb · Accepted solution]

So the scope is definitely receiving commands... With VICP, what happens when you try to run the Transfer Selected Waveform VI after manually acquiring a sweep on the scope? 

For LXI, the VISA Resource String is formatted TCPIP0::<ip address>::inst0::INSTR.   (You can find this out by going to the scope's IP address from your web browser;  a web interface is required by the LXI spec.)   I find that the LXI interface might not work right after rebooting (it needs to be reset)  so if you have problems, don't spend too much time using LXI for now.

Best Regards,

Alan

[swint144]

It works!  So what am I doing wrong when I just want to collect the measurement values, e.g. RMS, freq, etc?

[swint144]

OK, the transfer selected waveform VI works with both VICP (VICP::193.195.1.2) and VX11 (TCPIP0::193.195.1.2::inst0::INSTR).  I guess there's a bug in the "Acquire and Read my Measurements" vi?

[alanjb]

Hi Swint,

Make sure that your program is running the Initialize first...  If you are doing this, please email me your VI and I'll give it a look.

Best Regards,

Alan