Nice, so I'll get even more entertainment out of it!
The equipment that's bought and sold at the electronics flea market typically isn't used as a means to an end, it is the end. There's disappointment when you buy something there and it just works. There's no fun in that.
I'm blanking on the exact models I used; I'm fairly certain they were tds700s or tds71xx, but a lab I ran had about a dozen units and we had nothing "fry" in the 4 years I worked there. What applications would result in these catastrophic failures?
We had some "ghosting" on the displays on a few now that you mentioned it, but they were still 100% usable. I guess my expectations were lower since I never had to foot the bill for the lot of em (which at 20k/unit I guess I'd be upset about when one was faulty)
i thought maybe it was just something regionally here or the way people stored em, but i was in a position to refab many a few years ago and totally agree. tek had 100% repart rate and seemed like anything else (brand wise) was always in better condition internally even when way older.
I've got one, they are very cool. I also have a 7834 (storage tube), cool in a different way. On the other hand, they are taking up a lot of space... I also have two 485s, one with a broken trigger.
Thanks for answering, not surprising. I think the transition from all-hardware to Windows-driven digital hard on Tektronix and many other storied engineering teams.
Love this. I knew nothing about oscilloscopes until just a few months ago, when reasearched and bought one from a science lab. It wasfor a personal side project. I gutted it out and installed a mini PC inside, and now i run AI models into it. It's like my personal AI assistance. Hooked up to OpenAI realtime voice, grok bot, claude code, etc so I can command it to do stuff even when my main computer is off.
I just mainly love the retro-moder look of it. Here's a link to how it looks, for those curious:
I just had claude walk me through refurbishing a Rohde & Schwarz signal generator from the 90s. It feels pretty cool getting a multi thousand dollar piece of equipment for 60 bucks even if you have no idea what you'll use it for.
Yeah 1 GHz is nice, but that tiny 200 MHz Siglent is going to be much more useful in practice for most things.
Speaking of boat anchors, I'm trying to get my company to buy a DSA91304a (13 GHz scope with SERDES debugging). ~$44K with all the options, but still Windows-XP. The Windows-7 ones unfortunately don't have the options I want. Maybe there is a hack..
As I wrote: the TDS7104 is now sitting on a shelf in the garage, next to an Agilent 54831 and some other boat anchors. My daily drivers are a Siglent scope and a puny TDS220, which is about to be replaced by a TDS3052 that I'm bringing back to life. Hobbyists rarely need more than 100 MHz BW.
I hope you're able to thoroughly test that DSA91304a before dropping $44k on it!
Mine is a TDS224. Cheap, but I only use it for keeping my Eurorack synth going. 100MHz is overkill for audio. Although some modules use STM32 microcontrollers, so maybe the speed will come in handy.
200 MHz is good enough for most things. And for modern computing electronics even 1GHz is too slow, e.g. monitoring USB3 or high speed PCIE data lanes.
Did you get a price quote for that keysight oscilloscope? I see that you can also rent them for $2000 a month.
We've rented them in the past- always we're not quite sure we're done so keep them much longer than necessary. They're kind of a pain to pack and ship.
I went through a similar process recently with an HP/Agilent 54845A scope (1.5 Ghz, 8 Gsa combined) - a great tool if you need reasonably fast rise times and a reasonably fine time base resolution - the only issue is that it has an abysmally low sample memory for today's standards, so you get to see the trigger and "just a bit more". Well the other issue is that it pushes a lot of air... Like a lot, jumbo jet a lot. The scope luckily was in great shape and had a fresh test cert from not long ago.
I was going down the same route as the blog post (MSATA->PATA adapter), but simply imaging the HDD onto flash also didn't work.
The scope had to go into storage so I never finished this, but the SSD was being detected albeit at a lower capacity and no amount of twiddling with LBA and CHS geometry made a difference. My next step is going to be zeroing the drive, booting the scope with it as secondary, and then imagining it from within DOS/Windows. My hope is that the data will just end up at some offset. Or not even imaging it - just partitioning it, formatting it and doing XCOPY + SYS.
You may want to image the drive every so often and accessing the drive is a bit of a bastard (fewer than 32 screws on the HP but it's a pain regardless) - so it might make sense to actually get an SD->PATA adapter and mount it onto a PCI blanking plate, so that you can take it out easily. You may need a longer ribbon cable. There are also some 2.5 inch HDD brackets that mount onto a PCI blanking plate. Possibly a DIY job to replace the FDD with a plate that has the SD card mounted. Mine came with a ZIP drive.
I added the following software extras to the OS which I would recommend to anyone with an old scope like this that has an Ethernet port:
- An SNTP client so that you don't have to worry about the time and date (https://www.timesynctool.com/) - open source, win95 and up, just disable all logging to disk so as not to introduce extra writes and drive wear.
- TightVNC (1.3.10 I think) - a version that works on older Windows. Accessing it while the scope app is running slows things down significantly, so this is only for configuration changes and whatnot, also this particular scope writes directly to the VGA framebuffer, so you don't actually get to see the scope output via VNC!
- Shared some folders from the scope. This required a significant amount of fuckery to mount an SMB1 drive elsewhere without ruining one's existing Samba config, but it helps quite a bit to be able to exchange files with the scope.
Hardware extras that proved useful in a lab setting:
- One of those cheap VGA to USB frame grabber adapter things - they are detected as a video device, don't need drivers and you can watch your scope with VLC or your OS's built-in camera app.
- A remote-controlled power outlet. Speaks for itself - no need to touch the scope to shut down and restart an experiment from wherever you are.
- A GPIB to USB adapter if your scope has a GPIB/IEEE 488 port. Current Linux support is in a bit of a state, but anyway, this will allow you some degree of automation when reading the math / stats / other data, and will sometimes allow you to do more than the scope's UI will. I know for example that with GPIB I can control the signal on the AUX port on my scope, for which the GUI has no options.
- Not tried yet: this scope uses a PS/2 mouse (remember that they are not hot-pluggable) and a DIN keyboard. This bad boy: https://github.com/rasteri/HIDman - will let you plug in your wireless USB dongle and control your scope with your everyday keyboard and mouse.
The above significantly improves the "workflow" so that you hardly need to touch your scope or even swing your chair, or can use it remotely, and applies to most of the late 90s - early 2000s W...
A bit ago a semi-retired guy came back to help with some stuff including debugging serial ports. It was very cool to see him fiddle with the knobs and be like "oh those squiggles look good" "no that doesn't look right" etc. https://i.imgur.com/R5aEXbq.jpeg
Meanwhile total mystery to everyone else how to operate/interpret the machine but a lot of fun
10 GS/sec is very impressive as far as I'm concerned! One sample every 20mm or so at typical transmission line speed.
That said, anything with a floppy drive scares me because it undeniably indicates how old it is. My SDS7102V is no Tektronix, but an honest 1 GS/sec and at the time, under $200 on eBay.
I recently did something similar with a TDS7154B. Rather than going with an IDE/PATA drive I was able to use the SATA Gen1 ports on the motherboard and a molex-sata power adapter to use a modern SSD.
48 comments
[ 0.25 ms ] story [ 14.4 ms ] threadThe equipment that's bought and sold at the electronics flea market typically isn't used as a means to an end, it is the end. There's disappointment when you buy something there and it just works. There's no fun in that.
These are just exceptionally bad.
NuColor CRT displays going bad. Bad capacitors. Dallas NVRAM units battery running out of juice
Fried electronics are pretty rare.
Are there specific TDS models that you have found to be better, btw, reliability-wise?
I've got one, they are very cool. I also have a 7834 (storage tube), cool in a different way. On the other hand, they are taking up a lot of space... I also have two 485s, one with a broken trigger.
I just mainly love the retro-moder look of it. Here's a link to how it looks, for those curious:
https://x.com/slhomme/status/1965131874734584291
I had now idea there was such a huge second-hand market for those. It was such a great opportunity to learn about this tech.
I was initially confused how you managed to get amber and green screen together, but I guess you put an LCD in ..
Speaking of boat anchors, I'm trying to get my company to buy a DSA91304a (13 GHz scope with SERDES debugging). ~$44K with all the options, but still Windows-XP. The Windows-7 ones unfortunately don't have the options I want. Maybe there is a hack..
I hope you're able to thoroughly test that DSA91304a before dropping $44k on it!
Cute little thing. The reality is you hope that's all you need.
https://w140.com/tekwiki/wiki/Main_Page
Mine is a TDS224. Cheap, but I only use it for keeping my Eurorack synth going. 100MHz is overkill for audio. Although some modules use STM32 microcontrollers, so maybe the speed will come in handy.
100MHz is overkill for most hobbyists use cases, and definitely repairing test equipment: it's always the power supply.
Did you get a price quote for that keysight oscilloscope? I see that you can also rent them for $2000 a month.
You just can’t characterise power rail noise well with less than 500MHz of bandwidth.
I'm just wondering how difficult it would be to use a more modern bit of kit in there instead of the Celeron.
I was going down the same route as the blog post (MSATA->PATA adapter), but simply imaging the HDD onto flash also didn't work.
The scope had to go into storage so I never finished this, but the SSD was being detected albeit at a lower capacity and no amount of twiddling with LBA and CHS geometry made a difference. My next step is going to be zeroing the drive, booting the scope with it as secondary, and then imagining it from within DOS/Windows. My hope is that the data will just end up at some offset. Or not even imaging it - just partitioning it, formatting it and doing XCOPY + SYS.
You may want to image the drive every so often and accessing the drive is a bit of a bastard (fewer than 32 screws on the HP but it's a pain regardless) - so it might make sense to actually get an SD->PATA adapter and mount it onto a PCI blanking plate, so that you can take it out easily. You may need a longer ribbon cable. There are also some 2.5 inch HDD brackets that mount onto a PCI blanking plate. Possibly a DIY job to replace the FDD with a plate that has the SD card mounted. Mine came with a ZIP drive.
I added the following software extras to the OS which I would recommend to anyone with an old scope like this that has an Ethernet port:
- An SNTP client so that you don't have to worry about the time and date (https://www.timesynctool.com/) - open source, win95 and up, just disable all logging to disk so as not to introduce extra writes and drive wear.
- TightVNC (1.3.10 I think) - a version that works on older Windows. Accessing it while the scope app is running slows things down significantly, so this is only for configuration changes and whatnot, also this particular scope writes directly to the VGA framebuffer, so you don't actually get to see the scope output via VNC!
- Shared some folders from the scope. This required a significant amount of fuckery to mount an SMB1 drive elsewhere without ruining one's existing Samba config, but it helps quite a bit to be able to exchange files with the scope.
Hardware extras that proved useful in a lab setting:
- One of those cheap VGA to USB frame grabber adapter things - they are detected as a video device, don't need drivers and you can watch your scope with VLC or your OS's built-in camera app.
- A remote-controlled power outlet. Speaks for itself - no need to touch the scope to shut down and restart an experiment from wherever you are.
- A GPIB to USB adapter if your scope has a GPIB/IEEE 488 port. Current Linux support is in a bit of a state, but anyway, this will allow you some degree of automation when reading the math / stats / other data, and will sometimes allow you to do more than the scope's UI will. I know for example that with GPIB I can control the signal on the AUX port on my scope, for which the GUI has no options.
- Not tried yet: this scope uses a PS/2 mouse (remember that they are not hot-pluggable) and a DIN keyboard. This bad boy: https://github.com/rasteri/HIDman - will let you plug in your wireless USB dongle and control your scope with your everyday keyboard and mouse.
The above significantly improves the "workflow" so that you hardly need to touch your scope or even swing your chair, or can use it remotely, and applies to most of the late 90s - early 2000s W...
Meanwhile total mystery to everyone else how to operate/interpret the machine but a lot of fun
That said, anything with a floppy drive scares me because it undeniably indicates how old it is. My SDS7102V is no Tektronix, but an honest 1 GS/sec and at the time, under $200 on eBay.