¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: 2465 no traces, no OSD


 

> I checked this out again, and it's well inside spec. The ripple is "ugly" though, e.g. there are sharp spikes at ~20/40kHz. Assuming I get it working, I'll be planning to do the recap.
That is the normal sawtooth of a switching power supply.? As long as its low in amplitude you can ignore it and come back later.

> One surprising thing I found on a closer look; after I acknowledge the initial fault, something starts injecting about 40mV of a ~5MHz clock signal onto my 10V reference. Thankfully this doesn't propagate to the other rails though.
That sounds like the microprocessor clock.? 40 mv is small enough to ignore for now but I don't think it should be there.? It may be a clue to the erratic behavior you see on the controls.

>Thanks, this looks promising (not to mention fun:).
Are we having fun yet?? lol.? I wont be much help to you with the control board.? I know the generalities but my scope is a 2465 and I haven't actually worked on a 2467.? I hope someone with more experience here will jump in with ideas.? But the Tektronix Service Manual is very good on these scopes.? There?are Diagnostic Routines you can command from the front panel.??The service manual tells how to activate them and gives details of what tests are appropriate for your series of scope.? For my scope you activate the Diagnostic Routine menu by holding deltaT and delta V buttons then pressing Slope button on the front panel.? I would run them and see how it does.? Again, we are seeking easy information and others on this forum may have suggestions on which of these tests are important here.

>One thing I forgot to mention is that the scope doesn't trigger on the calibration signal, although the signal itself is fine viewed on my other scope.
Faulty trigger will have to be tracked down and repaired? But that should not cause the erratic panel operation you described before.? I would put that on hold until you get?stable operation.? One possibility is that trigger logic is controlled by the same computer that controls the panel.? Your trigger problems may clear up once the panel is stable.? The computer board (A5) sends controls that eventually reach?the trigger hybrid (U500) so you can trace these command lines with your test scope.? But, as I said,?check the processor first.

>I have to admit that I can't for the life of me figure out where the -1.25V reference comes from?
Sorry, I cant help you here since I have a different processor board and a different DAC configuration.? But in my 2465 scope the DAC voltage reference is derived by voltage divider from the +10 V reference from the Low Voltage Power Supply.? I will bet yours is similar.? Tek used a simple?resistor divider to set the voltages for the DAC input.? It has a 47 uf cap to filter is at the DAC input.

> (I'm a software guy, this is all alien territory to me).?
I did Hardware, then software, when they found out I failed at both they made me a manager.





From: tinkerer138
To: TekScopes@...
Sent: Wednesday, January 29, 2014 8:42 AM
Subject: [TekScopes] Re: 2465 no traces, no OSD

?
--- In TekScopes@..., machine guy wrote:
>
> GREAT NEWS.

:)

> Faulty power supplies can cause a variety of misleading symptoms but I don't think that is what is happening here.?? Double check the voltages on J119 and if they are reasonably close move on for now.?? Tek gives specs for an instrument that does laboratory quality measurements so small amounts of ripple are detracting.?? But you aren't looking for a small error.?? I suggest you find that first unless voltages and ripple are far out of spec and/or changing during operation.

I checked this out again, and it's well inside spec. The ripple is "ugly" though, e.g. there are sharp spikes at ~20/40kHz. Assuming I get it working, I'll be planning to do the recap.

One surprising thing I found on a closer look; after I acknowledge the initial fault, something starts injecting about 40mV of a ~5MHz clock signal onto my 10V reference. Thankfully this doesn't propagate to the other rails though.

>
> It sounds like you may have a control board (A5) issue.?? Since the case is open you can easily do a visual check of the A5 board.?? Look for leaking or bulging caps and check the date on the memory chip and its battery.?? The 246x scopes (except for the 2465 and 2445) used a battery backed ram to save memory contents.?? These batteries are known to fail after many years and must be replaced before all memory is lost.?? There is a procedure to do this replacement.?? Its necessary to provide temporary power to the memory chip while you remove the battery and connect a new one.?? Even a momentary loss of power to the chip will lose all contents and a full calibration will be necessary.??
>
Interesting, thanks.
I'm not seeing anything obvious to my eye, though I should probably take a harder look.

> A failing A5 or its memory could explain all the problems you are seeing.?? I suggest you??focus on that for now.??
>

Thanks, this looks promising (not to mention fun:).
One thing I forgot to mention is that the scope doesn't trigger on the calibration signal, although the signal itself is fine viewed on my other scope.

Staring at the circuit diagram, I figured many of the symptoms could be explained by a DAC or analog MUX failure. It looks as though the DAC/MUX is to the center of e.g. reading all analog signals, setting trigger levels, etc.
Working through the A5 test points, I find the CPU clock and the interrupt signals are just fine, as expected.

The DAC-derived reference(?) voltages at TP2420 and TP2421 are way off, however, so I've something to look into there.

I have to admit that I can't for the life of me figure out where the -1.25V reference comes from, though. It appears to be under CPU control through the DAC/MUX, but it's also used to derive the +1.36V reference, which in turn is the centerpoint of the DAC's I->V conversion resistors (I'm a software guy, this is all alien territory to me).

Anyways, I guess working forward from the DAC's reference is something to do :).



Join [email protected] to automatically receive all group messages.