03-21-2006 11:23 AM
03-22-2006 04:09 AM
Well, it is getting pretty confusing an affair. First, Tek makes an impression that TekVISA is indispensable. Now I found the following (readme-file for TekVISA by Tek):
1) Two distinct implementations of Virtual GPIB are provided: for NI-VISA version 2.5 or newer and for version 2.0 of TekVISA. In both cases, the Virtual GPIB resource is opened via the resource string “GPIB8::1::INSTR”.
2) The Virtual GPIB resource for NI-VISA 2.5 is a passport DLL.
And Tek support writes: “TekVISA includes NI Passport. That is an important component
towards simplifying TekVISA with NI applications and NI-VISA with Tek
utilities, however, it is not the answer to complete inter-changeability
of the VISA systems on all PCs and Windows scopes”.
Well, when I use NI VISA 2.6 and type “GPIB8::1::INSTR” into VISA resource, I get error: “The interface type (GPIB8::1::INSTR) is valid but the specified interface number is not configured”.
Advise, please.
Thanks,
Maxim
03-24-2006 10:38 AM
03-24-2006 11:21 AM
03-24-2006 12:00 PM
03-24-2006 04:04 PM
To GPIB Guru: I conclude that NI did not contribute to resolving the given problem since:
1) there hasn't been a replay signed by a "NI engineer" which would give me an unambiguous instructions;
2) I have sent an e-mail to NI support with a request for assistance more than a week ago and haven’t receive a response.
Regards,
Maxim
03-24-2006 04:31 PM
XBAND wrote: “I was able to talk with normal visa commands of LV7.1 by using the USB connection. I'm communicating with a Tek DPO4000, which has the Window's 2000 operating system. My only problem is getting data with more than 10k points. The scope has a setting for up to 10M points, I cannot get more than 10k through this communication , maybe it times out, but its funny that it is always 10k.”
- The limited number of waveform points possible to transfer from a digital scope is a usual problem for Tektronix as well as LeCroy windows-based scopes (perhaps unless classic GPIB is used).
I am afraid the reason is that their VISA (respectively XStream on LeCroy) API implements an object-model for the scope and the Microsoft COM (component object model) does not enable the “variant” variable to accommodate too big an array. Again, the producers should know, however they keep quiet on the details.
Regards,
Maxim
03-24-2006 06:48 PM
03-24-2006 07:38 PM
03-25-2006 02:43 PM
I would like to apologise to all the NI staff, who eventually contributed to the actual discussion, for failing to appreciate their valuable assistance.
Regards,
Maxim