Hi!
Years ago i have bought a failed tektronix TD540 scope that i'm tring to repair.
The unit failed due to the notorius capacitor leakage problem.
It's a long time project, as i've bought it years ago, then stopped as i had no more time.
In the last weeks i've put back my hands on, as i want it working.
When i've bought it i wasn't able to do a nvram backup (not remember why), so in any case i have to do at least a field calibration (i'm searching the needed isa pcii iia board). At that time, i've had only a acq. board failing the self test. So by now i'm using an nvram backup found on ko4bb archive.
Weeks ago, when i've put back my hand on it, failed to boot, due to some flashrom errors. So i've tried to do a backup of the flashrom content (desolder and resolder flashrom ics), then an update to the last firmware. The operation failed (i suspect due to a wrong firmware image), and also the backup was not good as reading one chip i have not noticed one little short between 2 pins. While programming the flash ic's, i've noticed that one of them was difficult to verify, so i've had the suspect that my problms were all due to a failed flash ic. So, thanks to an user here on the forum (chronos42), has provided me a new flashrom board with fw 2.09e.
Put it on, and the scope booted normally.
As the acqboard was failing with a really bad error (nothing read by the ram, returned always a lot of 0's, i think a failure with the mux), instead of trying to fix it, i've found another cheap not working TDS540 (missing the firmface board). So i've bought it, and after the cap replacement and a good wash to all the boards, i've tried to power it on with the working firmface board, and absolutely no boot.
So, i've tried to swap boards, and with my old logic board, "new" acq. board, "new" nvram i've booted it, but failed the logic board at the NvLibrariansDiag test. I not know if it's due to a mismatch between the nvram version and th fw version, or if it's caused by a NVram corruption. So, put the nvram with the backup found on ko4bb, and the logic board booted normally.
Now, the "new" acquisition and attenuation board are filing the self test, but with more reasonable errors. I remember that i'm running the calibration values of another unknown scope.... I not know if this can cause an acq. board failing the self test.
The errors that i get are:
ctlDiag ........................ ***FAIL***
..error details:
ERRORID: 149 diagnostic test failure ctlConfidencDiag
** 2.50e-9 <= exp <= 1.20e-8 actual= 0.00e-1 main TI failed
and
dacRangeDiag ................... ***FAIL***
..error details:
ERRORID: 149 diagnostic test failure Dac Range Test
** DAC system failure
The last one seem a failure with the DAC system.
The ctlConfidencDiag i really not know what is.
The scope show the trace on all the channels, with a little bias on CH1.
I've tried to do a probe calibration, and failed with the following error:
ERRORID: 108 Calibration failed Ch1 Probe Gain Error: -31.2%
Then i've tried to do an SPC on CH1, and i've got this errors:
ERRORID: 193 Characterized values out of bounds A/D biasing cal
ERRORID: 193 Characterized values out of bounds Vertical
t50f99ec: Finished characterizing Triggers
ERRORID: 108 Calibration failed Repet Cal Failed
And now, i need to search what is failing...
As already stated, i get correct waveform on all channels.
The scope can trigger, manually, as autosetting the waveform not works.
On CH1, depending on the attenuation setting, i have a varying offset, the other channels seem fine.
Now i play a bit more for trying if i find if at least spc and probe cal works on other channels, and study a bit what the DAC are used for, and if the is a way to chack it, or at least check traces around it for find is something was corroded.
Someone in the meantime have some ideas about my errors?
Thanks!
---EDIT---
Perfect! I have found an interrupted trace around C1641, and now the selftest stops a bit earlier at
vertRegDiag .................... ***FAIL***
..error details:
ERRORID: 149 diagnostic test failure ch3VertShiftRegDiag
** exp data= 1 actual= 0 for bit # 0 for addr: 0x72c021e
And the ch3 trace isn't showed anymore...
Where is the CH3 vertical Shift Register? Maybe it's not related to the trce that i've fixed, but it's nice that fix something, and something other fail...