My Keysight 1000X Oscilloscope FAILED - Page 1
Forum section: electronics / general

author: FERCSA
author_rank: Contributor
timestamp: November 16, 2018, 01:24:51 am
content: Dave, just connect your serial cable to the scope. You'll see more

author: scopeman
author_rank: Frequent Contributor
timestamp: November 16, 2018, 03:21:13 am
content: I wonder if there is a bad relay or solder joint that is common. Perhaps the calibration source? Probably no hope of finding schematics.I see a teardown and repair video in your future for this scope.Sam

author: mikeselectricstuff
author_rank: Super Contributor
timestamp: November 16, 2018, 08:42:36 am
content: You didn't leave any of the hack links set did you ?ISTR that offsets were one thing that made the apparent bandwidth increase hack not actually useful

author: PA0PBZ
author_rank: Super Contributor
timestamp: November 16, 2018, 10:08:17 am
content: I don't think that the calibration signal is what it should be. It is all over the place, so no wonder the poor thing gives up.

author: TK
author_rank: Super Contributor
timestamp: November 16, 2018, 12:32:44 pm
content: The calibration traces do not look that bad, in scopes that are functioning they jump all over as well, it is part of the calibration algorithm.Try removing the CPU/ASIC board, cleaning the contacts and re-installing it.

author: JPortici
author_rank: Super Contributor
timestamp: November 16, 2018, 01:35:16 pm
content: although when it moves around slowly it looks exactly like what happened to us on a batch of boards..There was this issue where a PWM signal was filtered with a two pole Sallen Key and the guy who drew the schematic forgot to put the capacitor between the positive input of the opamp and ground on one channel.It was ridiculous! the schematic was thight, if he had just copied the filter from another channel the infamous capacitor would have been on the title block, so he must have removed it never to add it back againAnyway, the issue was that besides worse filtering of the signal there was a heavily distorted oscillation when the duty cycle changed between zero and about 20%, of the same kind i saw on the video. I would inspect the calibration signal circuit to see if there are cracked caps or something. every time i did self calibration i never saw a signal like that

author: rsjsouza
author_rank: Super Contributor
timestamp: November 16, 2018, 07:45:36 pm
content: That was a throwback. It reminded me of the well worn out analog oscilloscopes of the university labs, where the amplitude level switches made the GND level jump around like a crazy monkey! The potentiometers and tappings on the front panel caused all sorts of glitches on the waveform.

author: ginbot86
author_rank: Contributor
timestamp: November 17, 2018, 09:12:57 am
content: I'm curious as to what the calibration logs have to say as to what went wrong. Using my Windows CE desktop hack (https://ripitapart.com/2018/10/15/gaining-access-to-the-windows-ce-desktop-and-doom-on-the-keysight-dsox1102g-oscilloscope/) I found that there are some .txt files (\Secure\cal\UserCal8Log.txt, \Secure\cal\callog.txt) and they provide some pretty verbose information as to the tests it performs, how long each test took, and so on.

author: FERCSA
author_rank: Contributor
timestamp: November 22, 2018, 12:31:59 pm
content: A lot of good ideas here, but we have to really see the serial log under the calibration process to see what's going on. ginbot mentioned the UserCal8Log.txt It's a copy of the serial log and you can access it without opening your scope, but probably your scope is already open

author: apl99
author_rank: Newbie
timestamp: January 20, 2022, 06:05:15 pm
content: Was the cause of the issue ever determined?

author: EEVblog
author_rank: Unknown
timestamp: January 20, 2022, 09:22:32 pm
content: Quote from: apl99 on January 20, 2022, 06:05:15 pmIt was the hack: