DSOX2000 and 3000 series - licence , have anyone tried to hack that scope ?

[TK]

Here are the latest patched firmwares, for the 1000X, 2000X, 3000A, 3000T, 4000X......

These firmwares have the usual patches for the license check and the 'unreleased/unfinalized software' things

*** Note:  ***
I have made these installs even EASIER, after the upgrade completes the install process will also make a backup of the oem lnk file that it installs during the upgrade, and then attempt to copy 'infiniivision.lnk' from the same USB stick you are doing the upgrade with...  so in otherwords, have your 'infiniivision.lnk' file READY, and on the root of your USB drive along with the patched firmware upgrade!
(this replaces having to telnet into your scope after the upgrade and having to put the .lnk file back on)

So have these TWO files on your USB:

1) infiniivision.lnk
2) upgrade_file.ksx


DSOX 3000A Series:  FW:  02.60.20201011001_patched https://mega.nz/file/KrAXRK6A#QwokNVJB4Hd_DDPU8r7F17wyygPHiqXWBBvBlXcKhC0
md5: <531BD46EF73E8C570922AF3AD4A9A8D9>

Please let me know if there are any issues with any of these!

Thanks PhillyFlyers, I did the patch on my DSO-X 3034A and it works!

I used the following infiniivision.lnk file:
93#"\Program Files\infiniiVision\infiniiVisionLauncher.exe" -l D3000BDLA -l BW50 -l SCPIPS -l SEC -l MSO -l MEMUP -l WAVEGEN

It is now upgraded to 500 MHz and includes the very rich D3000BDLA, which includes D3000AUTA, D3000GENA, D3000AERA, D3000PWRA, D3000NFCA, and all hardware based serial decoding (RS-232, I2C etc.), mask testing, video analysis, and even advanced math.

This is already great, again thanks.

However, the last 3 options in the file (MSO, MEMUP and WAVEGEN) did not work.
Did I do something wrong? It would be nice to have WAVEGEN and MEMUP... ;-)

cheers

MT

the number 93 is wrong. I counted over 110 characters in your lnk file

[Miketee]

Argh thanks TK, was wondering what  that number was... ;-)

Now I have:
122#"\Program Files\infiniiVision\infiniiVisionLauncher.exe" -l D3000BDLA -l BW50 -l SCPIPS -l SEC -l MSO -l MEMUP -l WAVEGEN

This installs MSO and MEMUP but not WAVEGEN. I checked the number of characters after # and it is indeed 122.

Bizarre. Any ideas?

[TK]

Argh thanks TK, was wondering what  that number was... ;-)

Now I have:
122#"\Program Files\infiniiVision\infiniiVisionLauncher.exe" -l D3000BDLA -l BW50 -l SCPIPS -l SEC -l MSO -l MEMUP -l WAVEGEN

This installs MSO and MEMUP but not WAVEGEN. I checked the number of characters after # and it is indeed 122.

Bizarre. Any ideas?

I don't remember if it includes the '#' character in the count.  Anyway, you can try moving the WAVEGEN option to the front and see what  happens

[Miketee]

You are right again. I moved SCPIPS to the end, now it loads everything except SCPIPS.

I don't even know what SCPIPS is... does anyone? I find nothing on Google.

Anyhow thanks, great forum, I will try to contribute some useful stuff here.

all the best

Mike

[Hexley]

Argh thanks TK, was wondering what  that number was... ;-)

Now I have:
122#"\Program Files\infiniiVision\infiniiVisionLauncher.exe" -l D3000BDLA -l BW50 -l SCPIPS -l SEC -l MSO -l MEMUP -l WAVEGEN

This installs MSO and MEMUP but not WAVEGEN. I checked the number of characters after # and it is indeed 122.

Bizarre. Any ideas?

I get 121 characters in your string; you might try with that number.

Also, you can trim the path from the filename. So this should also work, if you want to try it:

90#infiniiVisionLauncher.exe -l D3000BDLA -l BW50 -l SCPIPS -l SEC -l MSO -l MEMUP -l WAVEGEN

[Blue]

Thanks,

I just updated my DSO-X 3014A and it works. I'm very happy! 

I used:
90#infiniiVisionLauncher.exe -l D3000BDLA -l BW20 -l SCPIPS -l SEC -l MSO -l MEMUP -l WAVEGEN
with the 3000XSeries.02.60.20201011001_patched.ksx file.

 

[Venturi962]

Performed the 350MHz hardware mod / 500MHz license on my 4024A and now have a 500MHz bandwidth scope.  Rise times are in the 570 to 580ps range.  Stock rise times were ~1.30ns.

Some changes to the BOM originally posted by TheSteve:
https://www.eevblog.com/forum/testgear/dsox2000-and-3000-series-licence-have-anyone-tried-to-hack-that-scope/msg993078/#msg993078

Capacitors:
C1 - 2.2 pF 0603, 100V NPO, Murata # GQM1885C2A2R2BB01D, Digikey # 490-4838-1-ND, quantity 4 -> Marked obsolete, replacement 490-13316-1-ND
C2 - 2 pF 0603, 100V NPO,  Murata # GQM1885C2A2R0BB01D, Digikey # 490-6092-1-ND, quantity 4 -> Marked obsolete, replacement 490-8124-1-ND

Inductors:
I wanted to use the Murata parts, as they were available from Digikey and cheaper.  27nH Inductor is out of stock seemingly, so had to order that from Coilcraft directly.

L1,L2,L3 - 15nH 0603 2%, Coilcraft 0603CS-15NXGEU, quantity 12 -> Murata Equivalent, 490-15800-1-ND
L4 - 27nH 0603 2%, Coilcraft 0603CS-27NXGEU, quantity 4 (ordered direct from Coilcraft) -> Murata Equivalent, 490-15814-1-ND

Resistors: No changes

Under the shielding can the 4000 AFE looks somewhat different to the 3000 photos which gave some concern but turned out alright.

[TheSteve]

Nicely done!
The most interesting part is K504, it confirms they use a single PCB layout for 200 MHz to 1.5 GHz. If I ever get a 4000 series I will figure out the part swaps needed to mod to 1.5 GHz. It sure is hard to get a great deal on a 4000 series machine though, maybe Daniel has one he wants to sacrifice. I won't add any lights or water cooling to it though, just pure delightful bandwidth.   

[Someone]

Nicely done!
The most interesting part is K504, it confirms they use a single PCB layout for 200 MHz to 1.5 GHz. If I ever get a 4000 series I will figure out the part swaps needed to mod to 1.5 GHz. It sure is hard to get a great deal on a 4000 series machine though, maybe Daniel has one he wants to sacrifice. I won't add any lights or water cooling to it though, just pure delightful bandwidth.   

I remember some marketing material talking about a 1.5GHz 3000 series (extra bandwidth for USB2.0 measurements/decode) but it seems like that was pushed up/out to segment the market. Or perhaps it never quite worked reliably! Dunno.

[2N3055]

Nicely done!
The most interesting part is K504, it confirms they use a single PCB layout for 200 MHz to 1.5 GHz. If I ever get a 4000 series I will figure out the part swaps needed to mod to 1.5 GHz. It sure is hard to get a great deal on a 4000 series machine though, maybe Daniel has one he wants to sacrifice. I won't add any lights or water cooling to it though, just pure delightful bandwidth.   

I remember some marketing material talking about a 1.5GHz 3000 series (extra bandwidth for USB2.0 measurements/decode) but it seems like that was pushed up/out to segment the market. Or perhaps it never quite worked reliably! Dunno.

Not only marketing material. In some early manuals for 3000T series, 1.5 GHz was mentioned, and also realtime sampling and ETS is mentioned. I think it is just marketing segmentation.  There is a considerable difference between 4000 and 3000A series. 3000T is literally identical, simply a hardware variant of 4000.
It seems to me that, under pressure to refresh 3000 series line, they simply took 4000, removed one siggen ch, and crammed 4000 into 3000 case. It might be even that on siggen channel was removed simply because there was no place  for BNC.
But 1.5 GHz is not that much more useful than 1GHz (which goes to 1.1, 1.2 GHz anyways), and even with 1 GHz it is struggling not to alias with all 4 CH on. On 1.5 GHz they recommend to use ETS if you need all 4 ch to avoid aliasing.
If it had 4 A/D converters, than it would be different story...

[TheSteve]

The 3000T can certainly do 1.5 GHz - that is what my MSOX3024T currently shows
The 4000A is pretty much the same unit with the second AWG and built in VGA/Lan.
Going from 200/500MHz to 1/1.5 GHz requires quite a few parts to be changed(~160). I think it is very likely all of the same parts my 3000T needed but they are in different locations so it would take some time to verify everything. I have no doubt it could be done, just need a patient.

[Bud]

When you do such drastic upgrade, how's trigger stability go ?

[Howardlong]

Nicely done!
The most interesting part is K504, it confirms they use a single PCB layout for 200 MHz to 1.5 GHz. If I ever get a 4000 series I will figure out the part swaps needed to mod to 1.5 GHz. It sure is hard to get a great deal on a 4000 series machine though, maybe Daniel has one he wants to sacrifice. I won't add any lights or water cooling to it though, just pure delightful bandwidth.   

I remember some marketing material talking about a 1.5GHz 3000 series (extra bandwidth for USB2.0 measurements/decode) but it seems like that was pushed up/out to segment the market. Or perhaps it never quite worked reliably! Dunno.

While I understand the market segmentation aspect, a feature of the competitor Tek MDO3000/3 series is that the 1GHz/5Gsa/s model does USB 2.0 trigger/decode. I use this feature on the MDO4000, it's one of the very few reasons that scope even earns its place on the bench! FWIW, the MDO4000 also offers Ethernet 10BASE-T and 100BASE-TX trigger/decode, something that I don't believe the KS 4000 offers. However unlike the Tek 3/4 series, the KS 3000T & 4000 do offer USB PD.

[Someone]

Nicely done!
The most interesting part is K504, it confirms they use a single PCB layout for 200 MHz to 1.5 GHz. If I ever get a 4000 series I will figure out the part swaps needed to mod to 1.5 GHz. It sure is hard to get a great deal on a 4000 series machine though, maybe Daniel has one he wants to sacrifice. I won't add any lights or water cooling to it though, just pure delightful bandwidth.   

I remember some marketing material talking about a 1.5GHz 3000 series (extra bandwidth for USB2.0 measurements/decode) but it seems like that was pushed up/out to segment the market. Or perhaps it never quite worked reliably! Dunno.

Not only marketing material. In some early manuals for 3000T series, 1.5 GHz was mentioned, and also realtime sampling and ETS is mentioned.

... I was thinking back to the 3000A release!

[TheSteve]

When you do such drastic upgrade, how's trigger stability go ?

I suppose it is a drastic upgrade but the Keysight selfcal takes care of everything very nicely. The trigger stability isn't fantastic 1 GHz and above, but that seems to be all 3000/4000 series modded or factory.

[Sievil]

So have these TWO files on your USB:

1) infiniivision.lnk
2) upgrade_file.ksx


DSOX 4000X Series:  FW:  7.35.2020120823_patched  https://mega.nz/file/q3ABzQ5b#BH08CEf_Q0T7Z3kQMOzmHZTGubIGKPanCiq8my69TyM
md5: <04D0B52B8400F03B3EA87B90DE8FC004>[/b]

Please let me know if there are any issues with any of these!

Things went south my my MSOX4054A. "System concerns detected: -[2] Firmware update failed (aux -v)"
Now this message pop up even using the official firmware “4000X.7.35.2020120823.ksx”.

Before update, version : 2.xx (I can not remenber)
After update, version: 7.35
Yep, big jump, maybe this is how this flaut come ?

infiniivision.lnk : 38#infiniiVisionLauncher.exe -l D4000BDLA
 and
4000X.7.35.2020120823_patched.ksx

[wp_wp]

My friend has a DSOX3034A.
It has NAND corruption problem.
Now,I need 3000A v2.36 firmware to help my friend to repair it.
Can you send the 3000A v2.36 firmware to me?
Thank you.

[PhillyFlyers]

So have these TWO files on your USB:

1) infiniivision.lnk
2) upgrade_file.ksx


Please let me know if there are any issues with any of these!

Things went south my my MSOX4054A. "System concerns detected: -[2] Firmware update failed (aux -v)"
Now this message pop up even using the official firmware “4000X.7.35.2020120823.ksx”.

Before update, version : 2.xx (I can not remenber)
After update, version: 7.35
Yep, big jump, maybe this is how this flaut come ?

infiniivision.lnk : 38#infiniiVisionLauncher.exe -l D4000BDLA
 and
4000X.7.35.2020120823_patched.ksx

Wow, that is quite an old firmware you had on there!   Any idea how long ago that 2.xx firmware was installed?  or what year that is from?

I have no idea what that error could be, but that really is a large version jump... maybe you should try to find a version or two in between, like 3.xx or 4.xx?  wonder if anyone on here has a real old version you could try to go to, before going straight to 7.xx?

[TheSteve]

It would be good to connect to the internal UART while performing the firmware update, it will likely indicate what the problem is.
Also, did you perform the update with patched firmware or factory firmware? I'd always start with factory firmware first to verify it is all good.
I've never heard of or seen 2.x for the 4000 series and think it started with 3.x, went to 4.x and then quickly jumped to 7.x.

[kimwu]

Here you are 4000x firmware
InfiniiVision 4000 X-Series Oscilloscope v3.20
http://jays.co.kr/1_keysight/Oscilloscope-4000X.asp?layer=1
4000XSeries.04.08.2016071801.agx
https://drivers.plus/es/keysight-msox4032a-oscilloscope-firmware-4-08/273190/

that I can find old version in WEB

[Mark]

My friend has a DSOX3034A.
It has NAND corruption problem.
Now,I need 3000A v2.36 firmware to help my friend to repair it.
Can you send the 3000A v2.36 firmware to me?
Thank you.

This any good?
3000XSeries.02.35.2013061800.cab
https://www.dropbox.com/s/2jq5uskjo85smz8/3000XSeries.02.35.2013061800.cab?dl=0


I also have 2.37, but not 2.36. 

[wp_wp]

My friend has a DSOX3034A.
It has NAND corruption problem.
Now,I need 3000A v2.36 firmware to help my friend to repair it.
Can you send the 3000A v2.36 firmware to me?
Thank you.

This any good?
3000XSeries.02.35.2013061800.cab
https://www.dropbox.com/s/2jq5uskjo85smz8/3000XSeries.02.35.2013061800.cab?dl=0


I also have 2.37, but not 2.36.

Thank you,Mark.
I also have 2.35 and 2.37,but not 2.36.

[TheSteve]

There are some releases that were shipped with scopes from the factory but were never posted for download as they were superseded quickly. Usually one rev newer or older will still work to recovery the scope.

[TK]

My friend has a DSOX3034A.
It has NAND corruption problem.
Now,I need 3000A v2.36 firmware to help my friend to repair it.
Can you send the 3000A v2.36 firmware to me?
Thank you.

This any good?
3000XSeries.02.35.2013061800.cab
https://www.dropbox.com/s/2jq5uskjo85smz8/3000XSeries.02.35.2013061800.cab?dl=0


I also have 2.37, but not 2.36.

Thank you,Mark.
I also have 2.35 and 2.37,but not 2.36.

I fixed 2-3 scopes with the NAND issue and I don't recall having to match the exact firmware that was installed to recover them.  I know it is recommended in some posts, but I could not confirm it, as I repaired 2 scopes (probably with different firmware vesions) using the same USB drive

[analogRF]

My friend has a DSOX3034A.
It has NAND corruption problem.
Now,I need 3000A v2.36 firmware to help my friend to repair it.
Can you send the 3000A v2.36 firmware to me?
Thank you.

This any good?
3000XSeries.02.35.2013061800.cab
https://www.dropbox.com/s/2jq5uskjo85smz8/3000XSeries.02.35.2013061800.cab?dl=0


I also have 2.37, but not 2.36.

Thank you,Mark.
I also have 2.35 and 2.37,but not 2.36.

I fixed 2-3 scopes with the NAND issue and I don't recall having to match the exact firmware that was installed to recover them.  I know it is recommended in some posts, but I could not confirm it, as I repaired 2 scopes (probably with different firmware vesions) using the same USB drive

yes you are not alone. In the course of fixing mine I also realized the FW on the USB stick does not need to match whatever is on the scope. At least I think there is a good margin of error in terms of FW versions on the USB and in the scope