Contact an Expert

Thread: Communicate with 54831D Oscilloscope using LAN


Permlink Replies: 5 - Pages: 1 - Last Post: Apr 6, 2012 6:50 AM Last Post By: rayad Threads: [ Previous | Next ]
algoss


Posts: 615
Registered: 11/03/06
Communicate with 54831D Oscilloscope using LAN
Posted: Apr 4, 2012 8:49 AM
Click to report abuse...   Click to reply to this thread Reply
"Al, As you started here in this thread to discsuss LAN so I continue here. I already worked with low level sockets programming and can deal with it but as you said there are ready LAN routines in Agilent user programmer's manual and also have the files in my computer. The only thing that block me here is the O-scope I get it a used one and it has windows 98 on it and it seems it does not recognize our LAN, I tried to follow what they said in the manual to setup the ethernet: going to properties etc .... but I did not succeed to connect the scope to ethernet. Probably windows version is old and did not has some drivers .....
I think I should install windows 7 for example? is it risky to overwrite things or it can be done? "

Rachid,

I properly moved this discussion to a new thread.

First, the older oscilloscopes can not be upgraded to Windows 7 or even XP. The Motherboard can't handle it, and the scope FW won't work.

Under the scope interface is just a PC, running (in your case) Windows 95. Rather than using the LAN control capabilities built into the Scope FW, you should go to Windows and set things up the way you want. Attach a keyboard to the scope, and reboot it. Once it's running, use the "Windows" key (if the keyboard has one), or <CTRL><ESC> to get to the windows menu. Once you are there, you can use a cmd window, or Control Panel, to set the network parameters correctly. Verify that you have things set properly by using ping, both to and from the scope. If you can't get it working from there, then either the LAN port on your scope is bad, or you have some other problem on your network.

Al

Edited by: algoss on Apr 4, 2012 10:50 AM
rayad

Posts: 12
Registered: 04/04/12
Re: Communicate with 54831D Oscilloscope using LAN
Posted: Apr 4, 2012 10:34 AM   in response to: algoss in response to: algoss
Click to report abuse...   Click to reply to this thread Reply
Al, Thank you for the new thread.

Concerning windows, this is what I was looking for is to have the windows menu. I will try it tomorrow in the Lab. I guess switching to windows menu (windows key or CTRL-ESC) can be any time from the time the windows starts to boot?

I really apprecaite your long answers and I do not regret to register here because I was told it is a great forum.

Thank you, rachid
algoss


Posts: 615
Registered: 11/03/06
Re: Communicate with 54831D Oscilloscope using LAN
Posted: Apr 4, 2012 11:18 AM   in response to: rayad in response to: rayad
Click to report abuse...   Click to reply to this thread Reply
Rachid,

The best way is to wait for the scope to boot fully, including the scope application, then get the Windows menu. If you try it too early, you can interfere with the scope application. Please don't make any other changes to the Windows settings, besides setting the network up appropriately, and testing it.

Later scopes made Windows more easily accessible, by allowing the scope application to be iconified.

These days, we recommend that the user run Microsoft Update on a regular basis, and have some antivirus SW loaded. That was not easily possible or recommended back in the mid-90's.

Al
rayad

Posts: 12
Registered: 04/04/12
Re: Communicate with 54831D Oscilloscope using LAN
Posted: Apr 5, 2012 11:55 PM   in response to: algoss in response to: algoss
Click to report abuse...   Click to reply to this thread Reply
Al, Network is set now and I things were already set before. Just to find the IP to use it for commands communication because running the command "ipconfig" will open a window and disappear immediately and do not have time to look at the output and IP.

To start testing commands the examples files we have are done for windows nd I am working in Linux. Also it seems for example to open a connection (path descriptor) with the o-scope in the example they call a routine with IP address as input but it seems it's from a library that they created and I do not have this library for linux and do not also have the code to create it in Linux.

Rachid
algoss


Posts: 615
Registered: 11/03/06
Re: Communicate with 54831D Oscilloscope using LAN
Posted: Apr 6, 2012 6:31 AM   in response to: rayad in response to: rayad
Click to report abuse...   Click to reply to this thread Reply
Rachid,

To check the network settings on the scope, you need to first open a command window (Run 'cmd'), THEN execute ipconfig in that window. The window will stay open until you close it..

As for working in Linux...

I have never done SW development in Linux. I did quite a bit in UNIX, but that was more than 15 years ago. I have looked at the Application Notes on the Agilent Website, and there are some examples using both VXI and TCP for instrument control.

The concepts are the same as for Windows, just the actual implementation is different. You make a connection to the instrument, send requests, get responses, and eventually close the connection.

You should maybe open a thread titled, "Controlling a Scope from Linux". You might find someone who can help,but who skipped over this topic, since it's not really descriptive of what your issue is.

Al
rayad

Posts: 12
Registered: 04/04/12
Re: Communicate with 54831D Oscilloscope using LAN
Posted: Apr 6, 2012 6:50 AM   in response to: algoss in response to: algoss
Click to report abuse...   Click to reply to this thread Reply
Al, Yes also I worked using TCP/IP sockets and I can retrieve quickly old code I wrote for other applications. I just asked you probably there is somewhere a ready code to use now. I will open now the new thread.

Thank you, Rachid

Point your RSS reader here for a feed of the latest messages in all forums