copyright violation? the keygenerator has been NOT developed by Tektronix, so how can they claim that?
The AES key and option keys/values are in clear text visible, there is no need to "reverse" anything, therefore nothing
what one could "protect with anti-reverse copyright" whatsoever crap.
It is funny that Tektronix is veeeeery slow when goes to GPL violation or GPL source publishing, but that fast to claim
copyright on code that they haven't developed. There are keygen sources inside, not a single line belongs to Tektronix.
Does DPO3000 series work?
You need to have Python installed on your PC.
Skip the validate.py step, it's unnecessary.
On your PC, use gen.py with, as arguments, your scope model and serial number along with the wanted bandwidth and options.
python gen.py <model> <serial> <bandwidth> <options>
My python2.7, running according to the format described, appears the following situation, what is the reason? Thank you!
Dammed if I can get this to work but then I have never used python before, i want to open up my MDO3034
Question, where can I get the needed Python script?
I cannot find it. Please can you give me a hint where to get it?
Thanks!
Did anyone confirm that TEK LA cables are lossy? There are two types of probes in TEK list - active probes have a bit thicker wires and are for sure just non-lossy gang coaxial cables, and there are also thinner passive probes. Are the latter lossy? Anyone measured parameters? Or any references to their design?
You might even get away with fabricating an entire probe, but that inline resistance is in there for a reason, there's a really old Tek document about it somewhere that I can't locate right now, but it's also covered here http://www.dfad.com.au/links/THE%20SECRET%20WORLD%20OF%20PROBES%20OCt09.pdf.
There is a Circuit Concepts series. Page 15 of volume Oscilloscope Probe Circuits talks about the lossy cable.
I don't know if the Agilent/Keysight probes have this distributed resistance too, they do have a fancy woven cable on the two examples I have so I wouldn't be surprised.
It looks like they also use lossy cables. I searched on the web and found this in the 16557D logic analyzer card service manual.
The probe tip networks comprise a series of resistors (250 Ohm) connected to a parallel combination of a 90 KΩ resistor and a 8.5 pF capacitor. The parallel 90 KΩ and 8.5 pF capacitor along with the lossy cable and terminations form a divide-by-ten probe system. The 250-Ohm tip resistor is used to buffer (or raise the impedance of) the 8.5 pF capacitor that is in series with the cable capacitance.
hello.
I tried to do this but without success.
python gen.py MDO3012 C024186 500MHz AERO AFG AUDIO AUTOMAX COMP DVM EMBD FLEX LMT MSO PWR SA USB VID AUTO SEC
Could you please help me.
Thank you very much.
I had to use python2 instead of python3 when doing this.
In the mdo3evalpkg archive, folder gen must contain compiled version: gen.exe.
For me running command "./gen.py MDO3012 C024186 500MHz AERO AFG AUDIO AUTOMAX COMP DVM EMBD FLEX LMT MSO PWR SA USB VID AUTO SEC" give the result key:
EMCRY-AALYN-6BASY-62RB3-RS5RB-H
took me about 3 hours to figure how the generator works. all options activated on MDO3024 with 1.26sw
Is there a way to determine how many on / off cycles or hours powered up with this series of scope? I am not seeing an obvious option in the menus... Thanks
Self test menu certainly shows number of power cycles.
Pretty sure there is a power on hours counter lurking somewhere as well, I've had about a dozen of the bloody things.
I've got an MDO3104 here new in box with 3 power cycles and I'm not going to increase it just to check!
in all tek scopes from TDS3000 to DPO/MSO/MDO3000 and MDO/MSO/DPO4000/B/C
the hours and power on always show on the top of error log screen
in all tek scopes from TDS3000 to DPO/MSO/MDO3000 and MDO/MSO/DPO4000/B/C
the hours and power on always show on the top of error log screen
And IIRC the TDS2000B also.
Nice to see you here again :-)
Thanks. My MDO3000 has 1480 power-ups and 18109 hours of use. The weird thing about it is that the previous owner didn't bother to claim the DVM module, so it didn't have the feature. I wonder where it came from?
Thank you mk_ !
Slowly getting back on track after the 'Big Brexit Breakup' and my move to France.
I have things under my desk that need selling to fund renovation work....
Self test menu certainly shows number of power cycles.
Pretty sure there is a power on hours counter lurking somewhere as well, I've had about a dozen of the bloody things.
Yes, it's here:
I've got an MDO3104 here new in box with 3 power cycles and I'm not going to increase it just to check!
Might be interested, PM me if still available.
Hi, I have FW 1.24 and I generate the code , oscilloscope accept it without error but it says there is nothing to add?
When you restart the scope after adding the key, what is on the Utility => About => Application Modules and Instrument Options?
Presumably it accepted your key?
I have to say, I am gen-z and this is my first time in a community forum on a boomer-ass website. But man it was fun reading through the thread! Glad to say this hack still works.
I dug out an old MDO3012 in my college club space; updated the firmware to 1.30 and then tried the hack. It worked!!
PS dw if you don't have an option key for validate.py. Just go to Utility>About>Application Modules/Instrument Options. This and readme2 should be sufficient for you to figure out what to do.
How can this problem be solved? Does anyone know, big shots?