Author Topic: LAN Adapter for the Agilent / Keysight DSO-X 3000 & 2000 (Read 24217 times)

Jay_Diddy_B · « **on:** March 29, 2015, 10:45:27 pm »

Hi,

I was inspired to build a LAN adapter for the Agilent DS0-X 3034A Oscilloscope. This is not a new design I used a lot of the information available in this thread:

https://www.eevblog.com/forum/testgear/dsox2000-and-3000-series-licence-have-anyone-tried-to-hack-that-scope/

This is another excellent resource:

https://github.com/aewallin/DSOXLAN

This is a very useful picture showing the dimensions of the board and the placement of the edge connector. This was created by the forum member awallin.

Don't forget to check out Dave's teardown of an original:

http://www.eevblog.com/2011/02/17/eevblog-145-agilent-lanvga-module-teardown/

Updated Version July 2022

I have shared an updated version here:

https://www.eevblog.com/forum/projects/diy-dsoxlan-interface-for-keysight-oscilloscopes/msg4323223/#msg4323223

Here is my schematic, created using Orcad:

And pictures of the Gerbers. I like ZofZpcb 3D Gerber Viewer. I like that it colors different nets different colors. You can get the Gerber Viewer from here:

http://www.zofzpcb.com/

I made the board using my LPKF circuit board mill. Here are some pictures of the finished board:

To Be continued ...

Regards,

Jay_Diddy_B

Jay_Diddy_B · « **Reply #1 on:** March 29, 2015, 10:45:49 pm »

Testing

I connected the LAN port on the oscilloscope to the Ethernet port on my PC with a cross-over cable. This an Ethernet cable with two of the pairs crossed.

If you need details on how to make a crossover cable check:

http://www.cablesplususa.com/rj45-utp-guide.php

In this set up there is no DCHP, so you have to configure the LAN address manually.

You do this by going to the utility -> I/O -> LAN Settings.

I had to take the Config off Automatic and enter the IP and Subnet mask manually.

Note: The IP address that worked for me, may not work for you. You have to check how your Ethernet adapter in your pc is setup.

Web Browser Application

There is a web server in the scope. You can access this by entering the IP address on your browser. I had to install Java on my pc. You get security warning etc.

Here are some screen shots:

This first picture shows the Oscilloscope controls on the PC screen. You can operated the scope by remote control.

This shows the About Oscilloscope screen showing I have the Wavegen installed.

This shows the browser interface.

Issues

I have not found a way to set the manual IP address so that it is non-volatile. I have to re-enter the IP and subnet masks every time I start up the oscilloscope

. I looked at the teardown video. I don't see an EEPROM, so may be that is the way it was designed. Agilent may have assumed that you have DHCP on the network.

My computer Ethernet port does not like to connect to the scope automatically. I have to disable the interface and the enable to connect the scope.

Any ideas?

Modification

I need to add some mechanical support to the board to take the stress off the edge connector. I will make a small front panel and attach it with brackets to the board,

Regards,

Jay_Diddy_B

georges80 · « **Reply #2 on:** March 30, 2015, 02:05:33 am »

My MSOX2024 does NOT forget the IP address through a power cycle with my DIY lan board. Not sure why yours forgets...

I DO use a static IP for my scope.

cheers,
george.

georges80 · « **Reply #3 on:** March 30, 2015, 02:14:48 am »

... and here's my "happy" setup with static IP...

cheers,
george.

Jay_Diddy_B · « **Reply #4 on:** March 30, 2015, 02:26:16 am »

George,

Thank you for your reply. I am using version 2.35 which has that Agilent logo. On your picture I see the Keysight logo. Are you using a later version of FW? It could have been improved in a later version?

Regards,

Jay_Diddy_B

georges80 · « **Reply #5 on:** March 30, 2015, 02:29:09 am »

Version doesn't matter. I have 2.35 on my scope (flashed internally) and it works just fine with static IP. I can boot from a USB flash that has 2.39 and it also works fine with static IP.

I'm 'testing' 2.39 to determine if I trust it enough to flash it internally, hence the reason for running it from the flash drive right now.

cheers,
george.

Jay_Diddy_B · « **Reply #6 on:** March 30, 2015, 03:33:18 am »

George,

The problem I have may have been caused by a dirty RJ45 connector. I have cleaned the connector with alcohol and it seems to be working better.

The LAN configuration screen shows 0.0.0.0 until it connects, then it changes to the right address.

Jay_Diddy_B

georges80 · « **Reply #7 on:** March 30, 2015, 03:46:23 am »

Good to hear that it may have just been a bad contact.

Static IP is a good thing to have for an instrument

cheers,
george.

AndyC_772 · « **Reply #8 on:** March 30, 2015, 07:02:44 am »

Agreed... makes it much easier to find the instrument with a bookmark. I use DHCP with reservations for all the servers on my network.

Jay_Diddy_B · « **Reply #9 on:** March 30, 2015, 01:17:09 pm »

Hi,

More photographs to show. I reproduced the panel arrangement shown by dunkemhigh in this message:

https://www.eevblog.com/forum/testgear/dsox2000-and-3000-series-licence-have-anyone-tried-to-hack-that-scope/msg462272/#msg462272

This is my version:

This is a really good way of relieving the mechanical stress on the edge connector. I made mine using my LPKF mill. The copper clad board was plated using MG Chemicals' Liquid Tin.

http://www.mgchemicals.com/products/prototyping-and-circuit-repair/prototyping/liquid-tin-421/

Status

I get this warning message when the scope starts:

I am assuming that this is to be expected. The whole of the VGA portion of the board is missing.

I am able to use Telnet on the scope.

Regards,

Jay_Diddy_B

Monkeh · « **Reply #10 on:** March 30, 2015, 01:25:00 pm »

Quote from: Jay_Diddy_B on March 29, 2015, 10:45:49 pm

Testing

I connected the LAN port on the oscilloscope to the Ethernet port on my PC with a cross-over cable. This an Ethernet cable with two of the pairs crossed.

If you need details on how to make a crossover cable check:

http://www.cablesplususa.com/rj45-utp-guide.php

Alternatively, use a PC made in the last ten years and you won't need one.

DanielS · « **Reply #11 on:** March 30, 2015, 02:40:40 pm »

Quote from: Jay_Diddy_B on March 29, 2015, 10:45:49 pm

I connected the LAN port on the oscilloscope to the Ethernet port on my PC with a cross-over cable. This an Ethernet cable with two of the pairs crossed.

The majority of semi-recent Ethernet MAC controllers have auto-MDI/MDI-X detection. As long as either end of the data link supports it, cross-over cable become unnecessary.

As Monkeh said, nearly all PCs (and half-decent routers/switches) made in the past dozen years or so supports that.

Jay_Diddy_B · « **Reply #12 on:** March 30, 2015, 03:09:40 pm »

Monkeh, DannielS and the group,

I was foolish enough to read the oscilloscope manual which says:

I have tried a straight cable and I can report it works just as well.

[ I have learned from this. I will NEVER read a manual again

]

Regards,

Jay_Diddy_B

I am old enough to remember CAT4 cross-over cables.

Monkeh · « **Reply #13 on:** March 30, 2015, 03:14:59 pm »

That'll be because they don't support Auto-MDI/MDI-X, which is not uncommon for this sort of gear, and they're not assuming the availability of it on the PC.

But if you can afford an Agilent scope, you can sure as hell afford a PC with a gigabit card, and I have never met one which doesn't do it. Even most 10/100s from recent years are capable (as they're just crippled gigabit hardware).

georges80 · « **Reply #14 on:** March 30, 2015, 03:20:38 pm »

The "Systems concern.... VGA/LAN..." error message seems to occur for some/many people as indicated in the main 2000/3000 thread.

I do NOT have the error message and a few others also don't have it. I don't have it with the 2.35 or 2.39 firmware, so whatever causes and error to be detected is as yet unknown.

I certainly don't have a VGA on my DIY LAN card yet no error message...

The major difference (if it makes any difference...) is that on my board R3 = 10 ohms and C1 is 0.1uF (using your schematic's reference designators). I also have SH1 and SH2 connected together and via a 1000pF cap to the ground but that should have no functional implications.

cheers,
george.

Neganur · « **Reply #15 on:** March 30, 2015, 05:34:24 pm »

hey Jay_Diddy_B, what java version are you using to use that remote interface, an older version 7?

Jay_Diddy_B · « **Reply #16 on:** March 30, 2015, 09:21:33 pm »

Quote from: Neganur on March 30, 2015, 05:34:24 pm

hey Jay_Diddy_B, what java version are you using to use that remote interface, an older version 7?

I have tested with two computers. One has the latest version of Java version 8 upgrade 40. The other has version 6 unknown upgrade.

In version 8 I had to go to the Java setting and add the IP address of the scope to the trusted list. Without this I could not establish the link.

[RANT] Did I tell you that I strongly dislike (hate is a very strong word) the frequent updates from Java? On my machine it stops me seeing the bottom section of the screen by flashing away on the taskbar. I have lots of apps were the bottom of the screen contains useful information.... [rant\]

Does this help?

Jay_Diddy_B

AndyC_772 · « **Reply #17 on:** March 30, 2015, 09:27:56 pm »

Run the tablet interface instead; it's HTML5 and doesn't require Java at all.

fuzzoli · « **Reply #18 on:** October 20, 2015, 03:52:25 am »

What thickness PCB is the adapter? I'm thinking of getting a board made. Thanks - Frank

georges80 · « **Reply #19 on:** October 20, 2015, 04:31:40 am »

Standard 1.6mm/0.062" thickness.

cheers,
george.

benst · « **Reply #20 on:** March 26, 2016, 04:36:47 pm »

Would it be possible to also add the VGA output to this board? Or is it more involved than just wiring up the the connector?

Ben

AndyC_772 · « **Reply #21 on:** March 26, 2016, 05:04:20 pm »

It's not just a connector, there's an FPGA on the board as well which we assume is used as the VGA controller. I've no doubt it could be cloned, but it's a whole lot more effort.

benst · « **Reply #22 on:** March 26, 2016, 05:59:18 pm »

Thanks, good to know!

Ben

grouchobyte · « **Reply #23 on:** March 26, 2016, 07:17:28 pm »

Wish I would have known about this when I bought a fully loaded MSOX 3104 with the $400 LAN module.

Tell ya one thing, it "works a treat" as Dave would say. Agilent, err Keysight

Tek's MDO3k software and LAN performace when I compared it to the Agilent was beyond pitiful in 2013/14. Web browser control was a joke and hung the box everytime

I remember escorting the sales guy and the MDO to his car and politing telling him to come back when they replace the high school children they have writing software for their instruments, with professionals. In 2014 there is no excuse for lame LAN functionality like Tek released. They lost a sale that day.

millerni · « **Reply #24 on:** August 26, 2016, 12:37:39 pm »

Hi,

I already posted in some other tread, but I think this fits here as well.
I'm looking for a DOSXLAN Adapter to access the Telnet interface of my DSO-X...
Has anyone a PCB or even a stocked PCB left and would sell it to me?

matthieu.e is looking for one too...
If no one has some PCB's left, we were thinking about ordering some. Maby some one else is looking for a PCB / Module too..


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Author Topic: LAN Adapter for the Agilent / Keysight DSO-X 3000 & 2000 (Read 24217 times)

Share me