LabVIEW
Tektronix and labview interface through LAN
So what is the address and mask on your PC right now? I know someone told you what to set it to, but we need to make sure it's there, because this is the lead suspect in this case, followed by incorrect mask for PC and/or Scope.
@Bob_Schor wrote:
@crossrulz wrote:
@Bob_Schor wrote:
Ah, yes, Serial Communication using VISA. I don't do this often, but I've done it enough that I should be able to figure it out (with the help of the Tektronix Manual, of course).
Nobody in this thread mentioned Serial Communications. The OP is trying to communicate through TCP/IP.
The problem I usually run into with TCP communications is addressing is wrong, including the following:
- The instrument has the wrong address.
- The controller/computer in not in the same subnet. I use 192.168.0.XXX for my addresses to make sure everybody is on the same subnet.
It seems (to me) that the OP has TCP/IP set up correctly (he can "ping" the IP that he assigned to the Scope). This Scope uses either TCP/IP or USB to connect the Scope to a PC and uses VISA (over TCP) as part of the Protocol. [I've done this with Mettler balances, which also have TCP/IP outputs, useful as the balances were three floors away from the PC collecting the data]. The OP sent the standard "Who are you?" message (*IDN?), but (and here I'm guessing) hadn't set up Interactive VISA in MAX properly to read the response (or maybe forgot to read it -- it's been > 5 years since I worked with those Mettler balances, which are now about 400 miles away from where I am ...).
I think the OP is on the right track. But we need a VISA Guru (@crossrulz?) who has talked to VISA Instruments using MAX, with the manual suggesting commands (such as *IDN?) and how to get the responses (the part I don't remember).
Bob Schor
True, but the OP should be able to reach the scope through his browser.
Make sure the TCPIP passport is enabled in NI-MAX VISA options.
@Bob_Schor wrote:I think the OP is on the right track. But we need a VISA Guru (@crossrulz?) who has talked to VISA Instruments using MAX, with the manual suggesting commands (such as *IDN?) and how to get the responses (the part I don't remember).
Well, I am currently using a Tektronix MSO54. I doubt the interface is different other than some minor commands from the MSO64. Next time I'm in the office, I'll check to make sure there aren't any weird settings in the instrument to enable the TCP interface.
As already stated, verifying the connection through a web browser is the first line of troubleshooting. Just use MS Edge or Firefox and put the IP address of the instrument straight into the address and you should get a web interface. If not, you have a connection issue. Once that is verified, then move on the MAX and try to talk with it. *IDN? should work with this instrument.
@Bob_Schor wrote:
@crossrulz wrote:
@Bob_Schor wrote:I think the OP is on the right track. But we need a VISA Guru (@crossrulz?) who has talked to VISA Instruments using MAX, with the manual suggesting commands (such as *IDN?) and how to get the responses (the part I don't remember).
Well, I am currently using a Tektronix MSO54. I doubt the interface is different other than some minor commands from the MSO64. Next time I'm in the office, I'll check to make sure there aren't any weird settings in the instrument to enable the TCP interface.
As already stated, verifying the connection through a web browser is the first line of troubleshooting. Just use MS Edge or Firefox and put the IP address of the instrument straight into the address and you should get a web interface. If not, you have a connection issue. Once that is verified, then move on the MAX and try to talk with it. *IDN? should work with this instrument.
Great! In an earlier response, the OP did exactly that, sent the *IDN? request, but then got a VISA error on the Read command. It's been at least five years since I did VISA communication via MAX, and remember there were things I had to configure to read the response, but I don't remember the tricks. Could you help the OP with this aspect? I've also not connected to an Instrument via a Web interface -- your expertise and advice, again, would be helpful.
Bob Schor
If the command was sent as a query, the read was already executed and another read will give a timeout error.
@Bob_Schor wrote:I've also not connected to an Instrument via a Web interface -- your expertise and advice, again, would be helpful.
If an instrument has a LAN interface, it is likely LXI complient. Part of that standard is to have a web host as part of the instrument, making it controllable through a web browser. I know for sure the Tektronix MSO have this capability.
A couple things here.
Make sure the scope and computer are on the same network subnet as shown above.
Most modern instruments with a LAN interface are VX11 compatible. BUT you might have to enable VX11 in the scope somewhere (RTFM)
Start up NI-MAX and expand the Device and Interfaces part of the tree
Click on Network Devices and then click on Add Network Device at the top of the Right window (Or right click on Network Devices and select Create New TCP/IP Resource...
NI-MAX will then find your scope if it is on the same subnet and is VX11 compatible.
Your VISA resource will probably look something like "TCPIP0::192.168.0.6::inst0::INSTR"
Remember you can alway make a VISA Alias in NI-MAX for it too
