LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

problem with tktds7x4 getting started vi

I downloaded this driver from the NI site. Cant seem to get to work (using tektronix TDS 754a) the resoure name is not a problem as far as i know (GPIB::0::INSTR) only one instrument connected, the error message when i run the vi is always " Error-1073807302 occurred at tktds7x4 Initialise with options
Possible reasons: Driver status (HEX0xBFFF003A) Unable to start operation because setup is invalid (usually due to attibutes being set to an inconsistent state) Ive changed the values in each of the fields and still the same error.
any suggestions gratefully accepted,
Thanks,
Kevin Staunton
PS: Im very new to labVIEW
0 Kudos
Message 1 of 16
(3,387 Views)
As I see in you question "GPIB::0::INSTR" is wrong address. You double check with MAX there is no"GPIB::0::INSTR" Should be something like this
"GPIB0::1(or whatever)::INSTR". Check your GPIB connection. Check your SCOPE Talk/Listen Address. I think there is a option in the scope� OFF BUS" under utilities. May be You accidentally press this. Think that will help.

My suggestion: Another thing is if your Vi is for the End User who may not know about VISA address. I mean he or she may not know where to find the VISA address. Better look my example and you understand better.
Saw Naing Aye..
Download All
0 Kudos
Message 2 of 16
(3,387 Views)
You must be new to GPIB as well. Address 0 is the controller. The instrument will have an address somewhere between 1 and 30. The scope probably ships with some default set by Tek and you should look at the manual to see how to change it. To determine the current address, go to MAX (Measurement & Automation Explorer). Assuming that you've already done all of the installation and testing of the GPIB software, expand the Devices and Interfaces section of MAX and find the list for the GPIB card. Right click and it and choose Scan for Instruments. If everthing is hooked up correctly, the scope will be listed along with it's actual address.
0 Kudos
Message 3 of 16
(3,244 Views)
Even simpler is just the VISA control by itself. Clicking on the arrow of the control displays a list of detected instruments. No typing of anything is required and no requirment for any string parsing. You can also assign an alias to an instrument so instead of selecting GPIB0::12:INSTR, you can select, for example "Scope". Also, the latest version of VISA doesn't require the Open function. Just have the VISA write or read and go from there. If no session is open, one is created automatically.
0 Kudos
Message 4 of 16
(3,387 Views)
Could you please post the example VI that can detect the instrument. Thanks,
Saw
0 Kudos
Message 5 of 16
(3,387 Views)
The control by itself will list all available VISA Resource Names. Of course, this only works on the development system where you actually have the instruments. You also have the VISA Find Resource function which will return a string array of all devices.
0 Kudos
Message 6 of 16
(3,387 Views)
I think I understand wrongly. I know how to use MAX. I thought, your answer is VI that detect, something like that can perform MAX. YOu got what I mean. I mean If our Application VI is for the end user who may not know how to use MAX and he only know how how to Change the address of the scope. GPIB0::1::INSTR is may be confusing. Insted of putting GPIB0::1::INSTR, we put 1 only is more simple for the end user. Because in TEK scope, when we check the TALK/LISTEN ADDRESS, UNDER I/O then we can only see the bus is 1(or2or whatever) and we can also change the address from the scope. IN scope you cannot see GPIB0::1::INSTR. So that what I am trying to do. I thought your answer is in the VI we do not need to change the scope address and we can detect the availa
ble instrument. Think you know what I am trying to say. But anyway I know you are expert and I am new in LV think about 3 months only.
Thanks.
and If you have the VI that can perform something like MAX, I want to see and I think it will very useful.
Saw Naing Aye
0 Kudos
Message 7 of 16
(3,244 Views)
Okie thanks I got it. But now I am not in the lab to test this. Thanks.
Saw Naing Aye
0 Kudos
Message 8 of 16
(3,387 Views)
I still have a problem with the driver, I now have checked the correct resource name of the instrument in MAX(GPIB0::1::INSTR thanks!) but now when I run the VI I get the error "identification query failed". i tried the aliase as well but it is still the same error.
Any ideas?

Kevin
0 Kudos
Message 9 of 16
(3,387 Views)
My suggestion is try to use the IEE488.2 communicator and send some command like *IDN? or *RST and you should get some respond and if there is no respond there is something wrong with the communication.
And if you get respond, for my experience you may need to change the initialize VI. Try to run the other driver like, configuration horizontal VI or configuration Measurement and you will see some respond in the Scope. I think the problem is initializing VI. You may need to modify the initialize VI.
Hope that will solve your problem.
Saw Naing Aye
0 Kudos
Message 10 of 16
(3,387 Views)