| Electronics > Repair |
| Tektronix TDS5054B: Record Length Option: Solved! |
| << < (9/16) > >> |
| Jaak:
--- Quote from: Fractal on August 18, 2023, 10:21:18 pm --- --- Quote from: calibrationfixture on August 08, 2023, 05:56:10 am ---Hi Ko, I think these are the Scope Model Numbers to use for the TDS5000B Series: TDS5104B = TDS7216 TDS5054B = TDS7166 TDS5034B = TDS7146 I didn't have a TDS5000B Series on hand thus evaluations are appreciated. Greetings, Calibrationfixture --- End quote --- That totally did it on my 5034B; thank you very much! --- End quote --- Thanks for this! Fully optioned my TDS5054B. :) |
| calibrationfixture:
Hi alexandraquirosh, I cannot PM you, because (Zeroposter?) your Mailbox is full. Please empty it, or post your request in this Thread. Calibrationfixture |
| Circuitauger:
So I also happen to be having the exact same issue as KO, using a TDS6154C. I get the message "The new options and applications were not successfully installed", I will note however that typing in gibberish as a key yields the same error, furthermore if I type in a known good key I get the message that the option was successfully enabled, so I do not believe this is an issue with installing the key rather the key is indeed invalid. What I'm currently looking at now is how a known good key (like the one found on eBay) will validate and accurately be able to decode the model number and serial # however attempts to recreate this known good key will fail, in other-words taking the mask and other info from the validation and trying to apply it doesn't generate the same key.... Not sure why this would be as the ability to validate would mean you accurately know all the sbins? lol been a while since my crypto class. Additionally I've noticed at least the first 5 chars of the lic will not change for a given mask, so once you've picked a mask you can put any model number and serial (even all zeros) and it will remain the same so idk if this is a hint towards determining the proper mask for recreating the ebay key who's first 5 chars are "NHA5C" |
| calibrationfixture:
Hi Circuitauger, Allright, thus it is not a HW issue. Because using alternative Scopenumbers did work for the TDS5000B Series I hoped it also works for the TDS6000B/C series. Because I don't have these Models at hand, you were all invited. The same for DPO7000C and DSA/DPO/MSO70000(B/C) Series. Calibrationfixture |
| Circuitauger:
Well ultimately I do still think there's a good chance for this to work given that the validate.py is able to spit out valid info, and it sounds like from other posts that this works for both TDS5000 and TDS7000 scopes, so hopefully there's nothing weird about TDS6000 scopes. Probably looking at redoing w/e work shuvodutta did to discover the code mishandling the B variant. Sounds like they aren't contactable though. There's the post where you mentioned --- Quote ---I think these are the Scope Model Numbers to use for the TDS5000B Series: TDS5104B = TDS7216 TDS5054B = TDS7166 TDS5034B = TDS7146 --- End quote --- How did you determine this was the correct nomenclature to use? Also in this post https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/msg4617574/#msg4617574 --- Quote ---I used for my TDS7404B Option Masks: 10 44 FF FF FF FF FF FF FF --- End quote --- How did you generate that option mask? Looking in the option.py file, there's a description of masking but I don't see how your mask would be constructed. Thanks, -Circuitauger |
| Navigation |
| Message Index |
| Next page |
| Previous page |