ni-visa tektronix tds3054b via tcpip

[sclge]

No, I've been fighting with this for well over a month now. I feel like I'm going to be forced to take data by hand when I start to run testing on some circuit boards. Its just unbelieveable that my system worked previously but now it doesn't. I've tried multiple OS's, network configurations, VISA packages and two different scopes but nothing seems to solve the issue. Add Matlab, Tektronix and Agilent support both failing to help as well.

Of course if I ever figure out what is wrong I'll post it here. Just as of now, I'm completely cluesless. 

Robert

[slele]

Hi,

I finally could make the scope talk to the computer.

There was a TeKVisa LAN server control on the taskbar of the oscillioscope that had to be activated. I just selected "Start VXI-11 server" and MAX detected the scope :)!

Thanks!

Sneha

[jsuhr]

I had the same problmes and figured out a fix for me.

Simply you need a static Instrument IP address and turn off DHCP

My experience was....

Scope was set to DHCP and was auto assigned an IP and subnet in the correct range.
I was able to use a browser to connect via the Tek E-Scope by simply typing the Scope Instrument IP Address.
No other connectivity with Measurements and Automation panel or SignalExpress was possible.
I also was not able to use the Tek Openchoice software either.

I was frustrated trying to connect, so decided to try a Peer to peer connection following the Tek.com FAQ on how to setup a peer to peer.

For a crossover cable and dirct connection you need to do peer to peer

which is...
Connect the computer and scope with a crossover cable or plug both in to a network switch.
Disconnect from the network and other computers
You should only have connection between these two units
Scope (TDS3012C) utility settings turn off DHCP
Clear all settings under ethernet IP, DNS IP, Gateway, subnet mask address etc
For Instrument IP choose something like 128.181.240.130
Subnet mask 255.255.248.0
Leave other fields blank and turn off and restart the scope.

On the PC
Go to Network local area connection,  properties
under TCP/IP Enable use following address on Windows7 32 under TCP IPv4
128.181.240.131 use the same subnet mask 255.255.248.0
Enable "use the following DNS server address" but leave blank

Ping the scope's instrument IP address from the computer CMD to check.  (test connection on scope wont work) for instance "Ping 128.181.240.130"

Then I was able to connect using Measurement and Automation according to the normal setup instruction.
I had installed the newest download Tek version of SignalExpress from tek.com and the VISA 512 drivers from the NI site
Did not use the TekVisa
This is all Windows 7 32bit clean install of system as well.

After reconnecting the computer to the internet and letting the Windows 7 OS automatically change/correct the settings to connect....
I was still able to connect to the scope until I re-powered the scope and then it disappeared/error !  again from Measurement and Automation.

Back to the scope
Leaving DHCP off and setting the Instrument to a number outside the auto assigned ranges acquired from the IT person fixed the problem
for instance the range on our network is from 10.0.20.100 ~200
We used 10.0.20.60 on the scope to avoid future conflict
Subnet 255.255.255.0 since that is what the PC uses after reconnecting to the network/internet
Left other fields blank and now everything stays connected !

My symptoms seemed like the same as most here and the solution was a static IP and no DHCP

I imagine that everything else would be connected as well after this.

Hope that helps someone cause I spent 3 days on this !

[MrJackHamilton]

Yes, Simply turning OFF DHCP on the scope...leaving the assigned address works. My system is running using a router - works fine.

Wow, Much ado hassle about DHCP...which reminds me that you should NEVER allow such devices to 'float' on the network...HARDCODE your IP addressses.