Electronics > Repair

Tektronix TDS5054B: Record Length Option: Solved!

<< < (10/16) > >>

calibrationfixture:
Hi Circuitauger,

Using validate.py on a lot of existing TDS5000B License Keys leads me to the alternative and working Scope Numbers. The same with the TDS6124C and TDS6154C Models. Using validate.py gives TDS/DSA/DPO6124B and TDS/DSA/DPO6154B as Scope Numbers in case of existing TDS6000C License Keys, but these don't work as we know now. Maybe using DSA or DPO instead of TDS is the solution.

Using F's is the most time/cost effective way to enable as much as possible Options. A suggestion somewhere in the:

https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/600/

Thread.

Calibrationfixture

Circuitauger:
Alright actually got it, I suspect this is similar to the mod made to support B models

The clue was in trying to validate the known good keys for TDS6154C variants you’ll end up getting a UUID error:

--- Quote ---UID mismatch !
UID in key:     7C 29 00 03 0A 18
Calculated UID: 7C 29 00 02 0A 18
--- End quote ---
Which was suspiciously 1 off from what it should be... like C is to B

Basically the model number is getting expressed as a wrapped (maybe slightly scrambled) hex representation in the UUI
e.g. TDS6155C will yield a Calculated UID of: 7C 29 00 02 0B 18

So for anyone trying to repair their C variant scope in “key.py” you need to

change line 63 to

--- Code: ---mdl_int = int(model[3:].strip('C')
--- End code ---
And add after line 68 lines:

--- Code: --- if model[-1]=='C':
sn_int |= 0x03000000
--- End code ---

You should now be able to type in your model number normally as TDS6154C into gen.py

Of course for a long term fix which allows for B & C variants the proper way would be to check for a char as the ending value and apply the appropriate strip and hex value set (the above change to line 63 will break the code if you try to type in a B model number as it now doesn't know what to do with the 'B')

calibrationfixture:
Hi Circuitauger,

I think TDS6000C's are the only exception. With TDS5000B, DPO7000(C) and DPO/DSA/MSO70000(B/C) Models you always get only Digits as Scope Type.  By the way contrary to TDS5000B's the CRC mismatches on existing License Keys are seldom when using validate.py in splitting out the Option Masks.

Calibrationfixture

nicnac117:
Just a quick question ? Does any of this knowledge apply to a TDS5104 ?Your comments would be appreciated .

colorburst:
Yes, everything discussed here is applicable to TDS5104.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod