Tektronix TDS5054B: Record Length Option: Solved!

[shuvodutta]

I've acquired a Tek TDS5054B (Serial No. B022XXX) & in the process of repairing/restoring it (A write-up will follow.). It passes diagnostics & S.P.C. tests at present & shows probe compensation signal properly on all 4 channels (all credit goes to eevblog forum members, especially to TiN, Jwalling, thorswait, nsummy & magic), yet to perform detailed performance verification.

However, I'm unable to set record length to 16M (for single channel), it maxes out at 8M (8/4/2/) instead. TDS5054B comes with 16M (16/8/4) as default/standard option as per Tektronix product brochure & datasheet. Opt. 3M (for 16M memory) is not applicable for TDS5054B/TDS5104B.
(https://in.tek.com/datasheet/tds5000-series-digital-phosphor-oscilloscope & https://w140.com/tekwiki/wiki/TDS5054)

I've gone through various discussion threads here on eevblog forum but could not get any clear picture reg. this topic.

I've contacted Tektronix Tech. Support, yet to hear from them. I'll share their response here in this thread.

In the mean time, I was trying the Option Key Generator developed by other eevblog forum members; https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/msg484817/?topicseen#msg484817 (downloaded from here; https://0xacab.org/mitic/tek-ssc/-/tree/master as it's no more available on xdevs.com), it's supposed to work for TDS5000 series too. I tried to generate Option Key with 2M/3M (just to check) for my TDS5054B but the generated key was not accepted by the equipment. I tried to validate the default O.E.M. Option Key by using the validate utility provided with the tool, it detects the UID & Serial No. correctly but CRC fails. Probably TDS5054B uses a different CRC algorithm than CRC16.

It'll be great if someone can provide more details on this rather confusing TDS5054B record length issue.

Edit: Edited as per the suggestions received.

Last Edit: Fixed typo with one of the urls.

[shuvodutta]

I'm replying to my own post, hope someone will find the details helpful.

First of all, TDS5054B does need the Option for 16M (16/8/4) enabled/activated through 'Option Key'. I don't know why Tektronix has mentioned 16M (16/8/4) as default option in product brochure! (I've not received any response from Tektronix yet reg. this issue.)

As I've mentioned in the earlier post, the Option Key Generator did not work for my TDS5054B initially but it was the only viable option left for enabling the 16M Memory Option. I've decided to go through the code base (inline documentation helped a lot.) to find a way out. Even I've compiled a small data set comprising of Model No., Serial No., UID/Instrument ID, Option Key & Option Names from eBay Listings to have a better understanding of the key generation process. And the effort paid off, I could enable the 16M Memory Option (& many other software options) on my TDS5054B.

From reverse engineering, I've found that the existing code does not natively cater for the 'B' variant of TDS5000 series. With the help of the data set I've compiled & with some experimentation I could make it to work for my TDS5054B.

So, this utility works perfectly for TDS5000B series scopes too. I've not modified the code base yet to add support for TDS5000B natively but that won't be difficult (I'm not familiar with Python but the modification needs few lines only & is doable for me.). I may add the 'Augmentation Part' & put it in my github repo. (with the details I've reverse engineered from the Utility.) if it helps the community. In the meantime, if anyone needs help with the Option Key Generation for TDS5000B series, can send PM to me or can join the discussion here on this thread.

I would like to mention that the original work was done by other eevblog forum members, https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/msg484817/?topicseen#msg484817, I've just extended the feature set a bit. Without their excellent work it would never have been possible.

Edit: Edited as per the suggestions received.

[denimdragon]

I'm attempting to enable mine again. I might need your help. I need the CAN/LIN option 

[rommac100]

So for future people, I managed to figure the key code generator for TDS5054B. Feel free to DM if needed.

[shuvodutta]

So for future people, I managed to figure the key code generator for TDS5054B. Feel free to DM if needed.

I'm unable to send you PM as the Forum Software is throwing 'No Space left in Inbox' error!

[shuvodutta]

@user: VT7

I'm unable to send you PM as the Forum Software is throwing 'PM could not be sent to 'VT7' as their inbox is full!' error!

[LogicalDave]

@rommac100 We can't PM you because, as others have indicated, the forum says that your mail box is full.
If you have an option generator solution and wouldn't mind posting it here, that would be awesome.
Thanks!

[shuvodutta]

Just to update a few things,

Tektronix India has confirmed (after a delay of few months!) that Option Key is required indeed for using 16Mpts. memory option. I don't have any idea why they've mentioned it as default option in Tek. TDS5000 series product brochure.

I was in need of a set of front panel knobs for my TDS5054B, after a few discussions with Tek. India representatives (over phone & email, provided them the exact part no. from service manual), the request landed to my local Tek. vendor at last & I've never heard anything from them. I tried to follow up for a month or two & stopped afterwards. I felt they're not interested in selling/communicating to individual buyer like me who owns 'OLD' Tek. equipment (I personally own half-a-dozen P6245 Active Probes, P6046 Differential Probe & Keithley 2303 other than TDS5054B, I think my money is not good enough for them!  ), their primary target is large volume sales to big corporates; at least here in India.

@LogicalDave
Send me PM if you need any help with TDS5054B option key generation.

[shuvodutta]

Another Update:

Python v3.8 (on Ubuntu 20.04.3 LTS) breaks the Key Generator (mainly due to 'print' is now a function on v3.8 instead of a statement but there may be other issues/incompatibilities too.). I had to install python2 package (Python v2.7) to make it work again.

The command should look like (on a linux based system),

Code: [Select]

>>> python2 ./gen.py opt1 opt2 opt3


[pac1085]

Hi,
I hate to necro-bump this thread, but I can't get ahold of either of the people in this thread who mentioned having the modified script for the TDS5054B.  I'm curious if anyone else following this thread received a copy from either of them that they'd be willing to share with me?
Thanks!

[calibrationfixture]

hi pac1085,

Look at https://www.eevblog.com/forum/testgear/tek-csa7404-repair-project/msg4618210/#msg4618210

Posts Reply #715, 717 in this thread.

Succes,

Calibrationfixture

[pac1085]

Hi, I guess I'm not sure what you mean.  I can't even get the validate.py to run with the currently installed Options key.

This is what it gives me when I try it:

PS C:\Users\Philip\Downloads\tek-ssc-master> python.exe .\validate.py GX4ZQ-RZPST-M7RUT-5R957-NYT57-4UN2S-TR4H TDS5054B B010078
A6 EA EB DE 6D 30 AE FE 64 DC EF EF CE 6C DC 5D 4B 86 61 7C FA 00
03 5E 27 00 00 FE 1B 3E BD 50 A2 25 20 00 00 00 00 E8 41 E6 07 C9 10 04 00 00 00
UID mismatch !
UID in key:     5E 27 00 00 FE 1B
Calculated UID: 5E 27 00 02 BE 13
CRC: 61B9
CRC mismatch !

My understanding is that I should at least be able to get this script to run, to show me the options breakdown for the scope as it sits now.  I didn't see anything specific to the TDS5054B in the recent posts on the thread you linked?





Also, if I go on ebay and find a random TDS5054 (non-B) and use validate.py the same way, it seems to work.  So it seems like there is something wrong with the script in regards to the TDS5054B model (as mentioned by the OP)
PS C:\Users\Philip\Downloads\tek-ssc-master> python.exe .\validate.py 3XPA7-QNLTE-NNQ6E-4RS22 TDS5054 B030145
B9 36 D0 1D 53 91 30 E6 38 D1 0F 62 0C
1C C1 75 00 00 BE 13 57 A4 00 00 00 A0 50 10 00 00 00 00 00 00 00 00 00 00 00 00
CRC: A457
Key is valid, active options:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[calibrationfixture]

Hi,

You must omit "TDS5054B B010078".

These are only needed to generate a Key. The Program is universal.

By the way the "All Options Key" for a TDS5054B with B010078 Serialnumber is:

PHJHJ-M6G3B-2MZ86-9RPDU-2EYTK-NCVJ

Check:

PS C:\Users\??\??\Python\tek-ssc-master> C:\Python27\python .\validate.py PHJHJ-M6G3B-2MZ86-9RPDU-2EYTK-NCVJ
ED A0 83 16 37 39 E0 75 3D FF AF 0D 89 89 8D 89 89 89 00
48 5E 27 00 02 BE 13 DD A6 08 44 FF FF FF FF FF FF FF 76 34 14 10 00 00 00 00 00
This key is for UID 13BE0200275E (S/N 10078, model TDS/DSA/DPO5054B):
CRC: A6DD
Key is valid, active options:
08 44 FF FF FF FF FF FF FF 00 00 00 00 00 00 00 00 00

Succes,

Calibrationfixture

[pac1085]

Sadly it doesn’t accept that key.  It says the new options and applications were not successfully enabled.  Try entering the key again (I did a few times to make sure no fat finger)

[calibrationfixture]

Hi,

I read this Thread thoroughly and yes now I understand your problem. Because the Program works with the other Series (I also have a TDS5104) I overlooked it.

Except for the fact that the Key isn't accepted by your TDS5054B, the validate.py and gen.py Programs are working now as intended?

Another Member of this Forum had the same problem. I contacted him recently (thus in his case PM is working) for another issue, maybe he has now a solution for this:

https://www.eevblog.com/forum/testgear/tds5054b-options/msg1166628/#msg1166628

Succes,

Calibrationfixture

[pac1085]

Thanks, I managed to get ahold of another person who was familiar with it and they told me that I need to use like DPO7166 as the model number for gen.py.  Once I did that, it works.  I tried the option mask you listed, 08 44 FF FF FF FF FF FF FF 00 00 00 00 00 00 00 00 00 which also worked!

Question, does anyone know how to generate these option masks?  For example, how do I figure out what mask to use if I only want to add Option 3M, JA3,JE3,VNM,PW3 ? So I don't have a whole bunch of "App 69 avail, not installed?" in the options list?

Thanks!

[calibrationfixture]

Hi,

Look at:

https://xdevs.com/doc/Tektronix/TDS5000B/tektronix_options_sw_disk_1.dd

On this Disk you see several Option Software Packages. Installing the latest Version of the Scope Application Software (compatible with the MB of your Scope) also helps to enable additional Options. Using F's is the most time effective way to enable Options. Not all "App Avail: but not installed" are Options which can be enabled for your particulier Scope Series.

Succes,

Calibrationfixture


 


 

[Ko]

 I have TDS5034B which is different model from TDS5054B.
Is same model number DPO7166 is effective for it?
Do you know about it?

[calibrationfixture]

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

[Fractal]

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

That totally did it on my 5034B; thank you very much!

[Ko]

Thank you, Mr Calibrationfixture.
I have same issue to TDS6154C.

Do you know how to generate the correct code for this oscilloscope?

[calibrationfixture]

Hi Ko,

No problem to generate a Key for this Instrument. I assume you know how to use the gen.py Program. On this moment I am looking for the Recovery Disk(s) for the TDS6000B/C Series or an image of its HDD.

Calibrationfixture

[Ko]

I checked if gen.py can generate the valid code, however generated code can’t be used.
Of course I know how to use gen.py and validate as I have used it with 5034 and 7404 to get valid code.
For 6154 I tried to generate code by adding “00…” or some kind of changes but failed so far.
Can you advise me?

[calibrationfixture]

Hi again,

For a TDS6154C you must use TDS6154B and for a TDS6124C you must use TDS6124B as Model. That's all.

Greetings,

Calibrationfixture

[Ko]

I know the relations.
However the generated code is not accepted with the scope.
I think the cause is for the incorrect length of option mask or similar problem which I have experienced for TDS5034B.

Do you have any examples of option code for TDS6254C?