开云体育

Randu, In my case the error pointed to "demux 201" that I first interpreted as part of chip U200.? But I decided to spend some more time investigating and, after analyzing the memory contents, I was

Jorge and all, Just ran another set of Acquisition Area tests and the exact same failure as on 03/23 was registered, apparently pointing to U208 having an issue. I interpret this as meaning "U208 SRAM

The following photos have been uploaded to the TDS754D - repair images ( /g/TekScopes2/album?id=293963 ) photo album of the [email protected] group. * Tektronix TDS754D - startup

Hi Jorge, It seems my error logs and testing screens didn't attach - I just added a couple of them in the photos section of the forum, as before. All tests I ran seem to pinpoint the acquisition

Why do you think the acquisition memory is the problem? I am not able to see any pictures of the screen that are related to the problem. Have you posted them? I have a TDS754D that had a memory

Radu Bogdan Dicher <vondicher@...> added the photo album TDS754D - repair images ( /g/TekScopes2/album?id=293963 ) --- The following photos have been uploaded to the TDS754D -

Radu Bogdan Dicher <vondicher@...> updated folder *//TDS754D*

David, I don't really know, but per this: https://www.eevblog.com/forum/repair/tds-754d-diagnostic-test-acquisition-fail/ this one may not be one of those inflicted with this issue. Besides, here are

I don't then even tektronix will touch it now, it's probably at least 20+ years old. We also had a newer 5104, new about 6 years ago. After a year and a half it developed a fault on the input

Yes... but it's an option (the OP asked for options) ... and... AFAIK... that's what Tek does/did (probably before someone (Tek?) attempted a low level repair. (The DPO7000 scope (among others) is a

Is there somewhere reliable I could send this off to and have it repaired for a reasonable price other than Tekronix. I just use this for hobby, but would still like to have it working properly.

I believe that is one that needs all the capacities replaced on the Acq board and damaged traces repaired from the leaking electrolyte. wrote:

Not sure substituting a working acquisition board will be an option for many... We've got a DPO7104 work same issue at work. Didn't seem to affect anything on the scope, just needs the message cleared

Well, it seems to initially pass the tests after the module reseating, but now it's not (see enclosed). It seems to reasonably display a waveform though. So I guess I'll let it run for a while and see

Per the troubleshooting tree, I re-sat the A14D1 bus board and I am able to lock into waveforms on all four channels. But before whipping out the champaign, I need to note there's a time-induced issue

Also, here's a successful run of a signal into CH3. I've not yet been able to really determine how well any of the channels seem to be willing to display expected readings, vs. garbled and truncated

Here are some screen captures. "No signal in" shows the kind of scrambled screen I'm getting typically. There's a ton of garbage/artifacts in regular, idle run. Channel one seems to most diligently

Hi all, I got this scope in non-working condition due to failures of the A10 module (acquisition board). First time I turned it on, it ran and failed its startup tests. Since then, though, it'd start

Hi Paul, I assume you also ran Extended Diagnostics (more elaborate than Power-Up Diagnostics, Roy also mentioned this). Egge Siert

Paul, Only just now read above message. Even more silly question(?). Raymond