Version 2.41 can also have all features enabled without a lan card - details are in the last few pages.
Hi,
Thanks for the upload. I successfully updated my scope to 2.35. I now have to modify the .dll.
Hi,
I'm new in this Forum.
Found this Thread after I bought a DSO-X 2002 on Ebay.
Now I'm looking for a DOSXLAN Adapter to access the Telnet interface...
Has anyone a PCB or even a stocked PCB left and would sell it to me?
Hi,
I am looking for one too. I will perhaps launch a 5x batch. If it is the case I will tell you.
Send me a message if you find a way to have the PCB
Hi,
I successfully upgrade my dsox2002A to 200MHz with 2.35 firmware. I order a lan card and will receive it next week normally.
I have a question after reading the last few pages. Is the 500MHz mod from Memset is possible on the 2002A ? Thanks.
at least you cannot purchase a 350 / 500 Mhz DSOX2000 series scope from Keysight.
So probably you need to open your scope and check the PCB if it will allow such modification.
It is an interesting thought. I would think the front ends should be similar(but not the same, the 3000 series has a 50 ohm termination option). You would need to compare the strapping/jumper options and if they look similar enough try changing the jumpers to tell the scope it is 350/500 MHz. If it boots up and says the BW is 350 MHz then the software happens to support it and you will get the faster time base etc. Then you can look at the front end.
Thanks for the answer
Yes, I should look at the RF front end. I just reassemble my scope yesterday after my repair on the generator output
Is there any picture of the 2002A front end somewhere ?
Where is the strapping/jumper options area ? Inside the front end cover ?
Linked a photo of my scope.
I compared pics of the 2000 to the 3000 PCB(on the top side anyway) and the strapping resistors do look the same. So you you can trying swapping the same two parts as we did on the 3000 mod to switch the board to 350/500 MHz. Then boot the scope up and go to the about screen to see if it gives an error or says 350 MHz.
I haven't see any detailed pics of the 2000 front end as it is hidden under the cans - it will certainly be different then the 3000 front end but you never know what might be possible with some luck.
How hard can it be?
I just tried memset's method of installing the lnk file from a USB dongle:
MSOX3034A
- checkFirmware 2.41
- checkLink 63#\Secure\infiniiVision\infiniivisionLauncher.exe -l all -l bw50
- checkLoad the cab from the scope menu
- checkScope reboots but hangs either on the splash screen or the next one with the software warning
- no checkI understand what's going on in the recipe.xml file, it should work fine. Now I have to wait for my LAN kit to arrive
What could be the problem? Caps? I've seen people posting their links with either bw50 or BW50 so that doesn't seem to be the problem. Also, there's no CR/LF at the end of the link text if I'm correct? To be continued after arriving of the kit and some soldering... I hate to wait!
Shouldn't the link file be:
62#\Secure\infiniiVision\infiniivisionLauncher.exe -l all -l bw50
edit: - just looked back at the last few pages of this thread and it looks like the link Howard said he was using is wrong. As I posted above the character count is off by one, it starts after the # sign.
Should be an easy fix once you have your lan card.
N is 2-3 digits of length value of the following string, including '#' char.
63#\Secure\infiniiVision\infiniivisionLauncher.exe -l all -l bw50 is 65 bytes, so subtracting the first 2 gives 63... ?
Is it
"the following string, including '#' char"
or
" 2-3 digits of length value ... including '#' char"
English is a bit more flexible than code
I have no idea, but Howard's link seems to work and reading the posts I get the idea that the correct length does not really matter... anyway, hard to tell without the LAN adapter.
It is the number or characters *after* the # sign.
From the MS website:
[number of ASCII characters after pound sign allocated to
command-line arguments]#[command line] [optional parameters]
https://msdn.microsoft.com/en-us/library/ms861519.aspxAs to what happens exactly if the character count is wrong I can't say - but it seems quite likely it would lead to the problem you're having.
Perhaps Howard had some other character in his original file that wasn't carried over with a cut&paste.
Perhaps Howard had some other character in his original file
A cr/lf perhaps. That could make up the extra character and be ignored to boot.
Looks like telnet password is changed too. It is generated from instrument id now (still possible to get it, but I don't have a 3000T to try anyway)
Telnet passwd is changed on 3000T.Creatuseraccount need invoking get-model&sernm,doesn't like 3000A or 4000A.Shall we try to replace 3000T's FW with 4000A?
To be continued after arriving of the kit and some soldering... I hate to wait!
You can use any suitable cut of 0.8mm pitch PCB edge connector for urgent repair. Only one half of the connector is needed to get the LAN to work.
I've also put my scope to hang while working on the cab file. Without LAN adapter in hands I've cut a PCB edge connector line from crossfire connector of some old AMD videocard. It was the same pitch/thickness and almost the same width. All traces from edge fingers to the remaining part of PCB were carefully cut to make a clean connector. Next I've soldered short wires from connector to MagJack (only power and data lanes). It worked flawlessly and the scope was fixed via telnet.
Also you can attach 3.3V LVTTL RS232 port to scope's debug connecter (see the first pages of this thread for a pinout picture). By observing COM-port output you'll be able to find the exact problem with the lnk file. Probably you'll get an exception if your lnk file wasn't well-formatted.
Hi memset, thanks for joining in. I decided that I can wait a little longer (I have more scopes) but I indeed already looked into other options, including a temporary magjack connection.
I'm still wondering about the link, should the count include the # character or not? I included the # and the only reason I can think of why it went wrong is that it should not be included. However, the majority of the links other people posted include the # in the count, and even your 'empty' link in the zip file includes the # in the count:
48#\Secure\infiniiVision\infiniivisionLauncher.exeSo... what should it be?
So... what should it be?
Here is pin header pinout (wasn't found by me, check first pages for the source).
Find some 3.3V LVTTL level COM-port converter to connect to the board's TX and GND pins and take a look on the debug output (AFAIR its 115200 8N1).
DO NOT use conventional +/-12V COM/RS232 converters because you'll probably burn your CPU. The best choice is bare USB-RS converter like FT232R or PL2303H without companion level converter IC (NO MAX3232!)
I did use 72#\Secure\infiniiVision\infiniivisionLauncher.exe -l all -l BW20 -l SCPIPS
no cr/lf and the count 72 does not include the # that did work
If you use eg. notpad++ and select after the # to the end of line you can see the numbers (length) of the selection in the buttom bar of notepad++