Why I can not set or see the Tektronix TDS3054B available in Measure and Automation MAX 4.1?

[ATC_ATC]

At first I set the Tektronix TDS3054B with the Ethernet option & use it eScope with its provide IP address (192.168.16.65), it works very well. However, with the Measure and Automation MAX 4.1, even I try to use the VISA TCP/IP Resources -> Create New TCP/IP Resources -> Enter 192.168.16.65

After that I try to validate it or Open VISA Test panel ... I have error  message (see atttachment)

I also try to update Measure and Automation NI Product Updates but the result is the same

Does anyone knows the reason?

[pankaj]

ATC_ATC,

The first thing I noticed in your screenshot was you had an unusual name for the LAN Device name. The most frequent name would be inst0 but there could be others such as gpib0,1, etc (depending on which protocol is supported on the device for discovery). While adding the resource, could you use inst0 as the LAN device name and see if that helps? Another (easier) approach would be to connect the device on your subnet (where your host computer running MAX is) and  let MAX auto-detect devices on the LAN. See if either of these techniques help you and let me know.

Pankaj

[ATC_ATC]

Hi Pankaj,

I did try change LAN_ to inst0 but the result is the same (see attachment). One more thing, I can not use the same subnet with my PC (out of connections), however I did try with the Agilent device with the same IP address (same connection) and it worked fine. Therefore I think it is not the main reason

In order to show you more detail, I attach the config. screen of the eScope from Tektronix that I remoted control through this IP address, might be you see some thing different.

Regards

[pankaj]

ATC_ATC,

Could you try gpib0 as the lan device name. I saw on their manual that they use gpib0 for their interface. Let's give that a try before we look at other possibilities.

Pankaj

[ATC_ATC]

I am sorry about the confusion, this morning when I start to work and try it again (as the last setup I sent to you), it work fines! I think that I have to restart the computer to update the LAN setting

Thanks for the advices

[Sito_1]

Hi, I'm hoping someone will be able to help me. I have been struggling with the same problem as stated above by ATC. I was able to communicate to the scope yesterday, after I updated the firmware to rev 3.41. I was able to validate the Visa session. However, this morning when I came in, I'm back to where i started yesterday, struggling to connect to the scope. Nothing has changed, except that the scope was turned OFF last night.  I'm using a TDS3024B. But I'm receiving the same error. Does anybody have any idea why this might be able to come back? The error received when I try to validate is "Could not Open a VISA session to "TCPIPO::172.18.162.43::inst0::INSTR VISA error code 0XBFFF0079. The protocol specified is invalid."  Any help would be greatly apprciated. Sorry for posting to such an old thread.

[Eric_K]

Sito_1,

Can you double check that the IP address of the instrument has not changed and that there in not another system on the network with the same IP causing a conflict.  You could also try using gpib0 as the lan device name as pankaj suggested.  You may also have better luck creating a new forum post.

Eric K

Applications Engineer

National Instruments

[Sito_1]

Thanks for your quick response Eric. For anyone that has the same issue as I did with the Tektronix Scopes TDS 3000  series, just make sure that the DHCP/BOOTP is set to OFF in the Utility Menu, when first trying to connect to the unit.  Setting the DHCP/BOOTP settings to OFF then reboot, then try to connect using MAX, also use inst0.  This finally worked for me.  And to answer your question Eric, the IP address did not change as I was able to see the "web page" *escope page for the scope and I was able to send it commands via the *escope mode.  Many Thanks!

-Wilson V "Sito"

[yytseng]

I got the same problum. And solved by setting the DHCP and BOOT to OFF, and Reboot the TDS3000. 

this method does work!!

[davide_bad]

Hi to all!

I would like to add my experience and the "workaround" which I found to solve this problem.

Context: I developed an application to make some automatic measures (LabVIEW 8.5.1) using a waveform generator and the TDS3054B Oscilloscope through the ethernet LAN.

I have choose a fixed IP for the TDS3054B but this didn't solve the problem.

The PC comunicates with the oscilloscope with in a 100 Mb LAN.

I HAVE INSERTED BETWEEN OSCILLOSCOPE AND LAN, AN OLD "10BASET" ROUTER  which works ONLY WITH 10 Mb of speed, so that the comunication between the Oscilloscope and the LAN is FORCED to 10 Mb rather than the maximum of 100Mb.

With this configuration ALL WORKS FINE!
----------------------------------------------------------