| Products > Test Equipment |
| Someone has hacked MDO4000C? |
| << < (4/18) > >> |
| Howardlong:
--- Quote from: andyturk on April 02, 2018, 10:02:36 pm ---Note the sticker. :-/O --- End quote --- I have a similar result on an MDO4054C that I recently purchase, except that after upgrading the bandwidth, I get a permanent "WARNiNG: This oscilloscope is not compensated." SPC also consistently fails after two minutes. If I remove the bandwidth option, reverting to 500MHz, all is fine again. Edit: my unit has MB HW ID 7, and AFE SW ID of 2. It is an MDO4054C with SA6 factory fitted at manufacture. For fully loaded but original bandwidth: gen.py MDO4054C C###### 500MHz DVM DDU AFG MSO TRIG EMBD COMP ENET USB PWR AUDIO AERO AUTOMAX LMT VID SEC For fully loaded with 1GHz bandwidth: gen.py MDO4054C C###### 500MHz DVM DDU AFG BW5T10 MSO TRIG EMBD COMP ENET USB PWR AUDIO AERO AUTOMAX LMT VID SEC |
| Howardlong:
--- Quote from: abyrvalg on March 30, 2018, 11:24:18 pm ---https://0bin.net/paste/tZYZ4Fs5rjqvAoza#+yNeuILPU-nQmgFvDixaTsFyVclm2Mnh2gr2Id/aSBL --- End quote --- I think there is a little bug when using this for the MDO4000C in the way it determines the key to use: as it stands, it will always generate MDO3000 keys if you specify an MDO4000C. I am not a Python programmer, but I hacked the code for key.py to comment out the MDO4000B for my purposes, I suspect an elif might be a better longer term option. The problem was that although the 4000C key was correctly selected, it is immediately overwritten with the MDO3000 key. Original key.py: --- Code: ---# generate an option key def encode(model, sn, mask): if model.startswith("MDO4") and model.endswith("C"): k = mdo4kc_key if model.startswith("MDO4") and model.endswith("B"): k = mdo4kb_key elif model.startswith("MDO"): k = mdo3k_key else: k = dpo3k_key uid = GenerateUID(model, sn) --- End code --- Hacked key.py for MDO4000C and MDO3000 only: --- Code: ---# generate an option key def encode(model, sn, mask): if model.startswith("MDO4") and model.endswith("C"): k = mdo4kc_key print "mdo4kc_key" # if model.startswith("MDO4") and model.endswith("B"): # k = mdo4kb_key # print "mdo4kc_key" elif model.startswith("MDO"): k = mdo3k_key print "mdo3k_key MDO" else: k = dpo3k_key print "mdo3k_key default" uid = GenerateUID(model, sn) # find first leading 1 bit --- End code --- |
| tv84:
--- Quote from: Howardlong on July 21, 2019, 10:04:11 am ---Original key.py: --- Code: ---# generate an option key def encode(model, sn, mask): if model.startswith("MDO4") and model.endswith("C"): k = mdo4kc_key if model.startswith("MDO4") and model.endswith("B"): k = mdo4kb_key elif model.startswith("MDO"): k = mdo3k_key else: k = dpo3k_key uid = GenerateUID(model, sn) --- End code --- --- End quote --- The "correct" correction should be: --- Code: ---# generate an option key def encode(model, sn, mask): if model.startswith("MDO4") and model.endswith("C"): k = mdo4kc_key elif model.startswith("MDO4") and model.endswith("B"): k = mdo4kb_key elif model.startswith("MDO"): k = mdo3k_key else: k = dpo3k_key uid = GenerateUID(model, sn) --- End code --- I think this what the original programmer intended it to be. |
| Howardlong:
Like I said I’m not a Python programmer! |
| Howardlong:
I can get rid of the red compensation banner temporarily by enabling factory pass from the calibration memory. However after a reboot it returns. To remove red "WARNING! This oscilloscope is not compensated." banner after each boot: * Login with telnet, note commands are sent in the blind: --- Code: ---telnet <scopehostname> 4000 :PASSW TRESPASS :DEV:MOD 1 --- End code --- * Then, on the scope: Utility -> Calibration -> Factory Cal -> Always Pass: Yes * Finally, optionally from telnet to remove the new menus: --- Code: ---:DEV:MOD 0 --- End code --- Tonight I managed to do a factory calibration, and immediately for the first time a successful SPC. Being my first time, the whole process took me about two hours, but I had to build a 24Vpp amplifier for my AWG which maxes out at 20Vpp. However, after a reboot the red compensation error banner returned. I suspect I may need to lock the calibration afterwards? Is anyone familiar with recent Tek scope calibration processes? Is there something one should do after a successful cal and SPC? |
| Navigation |
| Message Index |
| Next page |
| Previous page |