09-08-2010 01:40 PM
I am using Labview to control Oscilloscope TDS 2014. I downloaded the plug in and play driver from http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=540. I want to test the connection between the driver and the instrument. For this, do I just run the getting started VI? Do I also need to alter the default values in the VIs or change anything?
Solved! Go to Solution.
09-08-2010 01:52 PM
What "getting started" vi are you referring to? I don't see one in the driver that you downloaded. If you downloaded it and installed it as the driver page explained then you should find under your instrument i/o palette on the diagram page an instrument drivers sub-palette. Or if you go to the directory that you have LabVIEW installed you should see an "instr.lib" directory, where your driver for the TDS should be installed. Within it there should be a file "Tektronix TDS 200 1000 2000 Series.lvproj" which is a LabVIEW project. Launch that and you should see a folder "Examples"
-
09-08-2010 02:49 PM
There is a "getting started" Vi in application examples sub-palette under the instrument driver sub-palette TKTDS 1K2K. How do I test the connection between the installed driver and the oscilloscope. I am trying to run the getting started Vi. Is this the way to test and should I alter the default values in the VI or just run it?
09-08-2010 04:04 PM
what interface are you using, GPIB, USB, serial? Do you have MAX (Measurement and Automation eXplorer) installed? If yes, see if you can see the scope in that under "Devices and Interfaces" (you will need to have it installed for LabVIEW to talk to most instruments, etc.). If you can see the instrument then you should be able to use the test panel that should be available when you select your instrument ("Open VISA Test panel") to try and communicate with the scope, if only a *IDN?\n which sends a pretty standard query over the interface asking the instrument to respond with its indentification info (frequently model type and serial number). If you have that then you should be able, selecting the instrument in the visa pull down on the LabVIEW demo software in the the driver you installed, to "play" with the scope. MAX provides a way to test the hardware connection before spending anytime trying to figure why LabVIEW code does/doesn't work.
09-14-2010 08:45 PM
I am using a serial RS-232 interface. The MAX shows the list of ports and I configured the port as well but I dont see the oscilloscope.
09-14-2010 10:30 PM
You aren't supposed to see the scope listed. All that you will ever see is the com port. What was the result of the *IDN? query?
If you get a timeout error, you might want to try \r\n as a terminator. Also verify you have the correct cable. I think you need a null-modem cable.
09-16-2010 06:10 PM
The cable I am using is null modem. The result I get for *IDN?\n and after executing viread is TEKTRONIX,TPS 2014,0,CF:91.1CT FV:v10.20 TPS2PWR1:v1.00\n
For query?\r\n , I get return status error as BFFF0015.
When I try to run example VIs in the instrument driver Vi, I get error as BFFF0072 or BFFF000E.
09-16-2010 06:27 PM
OKI, getting that after the *IDN?\n is a very good sign, it means you are talking to the scope, have the com settings and cable setup correctly. Not sure what the query?\r\n is though. Can you attach an image of the error (in .png format, "paint" will save as .png). If you can attach either the example vi, or an image of its diagram that might also help.
09-17-2010 03:51 PM
I tried to run the example VI of instrument driver VI and also one simple VI, and I got an error. I have attached the example VI snapshot and the another VI file. The error seems to be in VISA read block in both the cases but couldnt figure out how to get rid of this error.
09-17-2010 05:27 PM - edited 09-17-2010 05:28 PM
The posted VI will not work because you are not sending a termination character. You are sending the strings '\' and 'n'. Right click on the string control and select '\' Codes display and reenter the command.
The example probably does not work because it is GPIB only. You would need to run the initialize function. You should also be using the newer project style driver. Those examples do have the initialize function and you probably would have been working by now.