My problem now seems to be intermittent. The CH4 offset issue comes and goes, with some dramatic screen glitches on the CH4 trace.
Check your probe for an intermittent X1/X10 switch - out of my two DS1054Z, I have three probes with chronic switch issues on the X1 position and two or three more I wouldn't trust either.
As for the offsets, the channel offsets on both of my scopes jump around depending on which channel combination is enabled and some channels drift by as much as 2/5th of a division over time. Some people have said offsets can even vary depending on the order channels are enabled but I have not noticed that specific quirk on mine.
Nope, it's not the probe(s). Actually all 4 of my probes seem fine, switches work, springhook clips have their insides, etc. When it decides to glitch, the CH4 glitch is there even when no probes at all are connected and the scope is just running along in "Auto" trigger showing channel baselines, as long as the channels aren't "Ground" input-coupled. It seems to have gotten worse over time, too. I'm afraid I'm going to have to return it.
What's really odd is that when it's _not_ glitching, the CH4 is the most stable and lowest-noise of the 4.
The amplitude of the glitch is much greater when 5V/div is selected, and almost goes away when 2V/div or lower is selected, until really sensitive settings in the tens of mV are selected.
(Also tested with and without the 100MHz and other features "unlocked", no effect on glitching.)
So Monday I'll be talking to TEquipment to see what we can do about getting a replacement unit, hopefully sent to MY house not the vacant one next door.
ETA: Could it still be a software/calibration issue? It was glitching almost continuously a little while ago, so I decided to try the self-calibration Yet Again (probably the 5th time I've done it, always after thorough warm-up (and with nothing connected to any inputs, as per the Manual instructions and the Big Note that comes up on the screen, heh...) and now it's running along with CH4 perfectly stable and low-noise, only a tiny offset of about 1/2V in 5V/div vertical scale. See the screenshot below, in Pass-Fail mode waiting for a glitch to come up. No probes connected.
I think that the reason it updates more slowly when a "fail" waveform is detected, as Dave noted in the video review, is so that the user has time to Stop the scope and do a screen capture before the glitch disappears. Here I've got it set to Stop on Fail, and if/when it does I'll capture that in a screenshot.
@Corporate666:
Hopefully I'll remember "I like the way you think!" if you ever have a post about being scammed, etc.
Humor-deficient, are we? Can't recognize a joke? As a "newbie" I did not feel right responding with outright criticism of the suggested theft, as you have done, so I responded instead with a little attempt at humor while still rejecting the suggestion-- which I think was probably a joke in the first place. As I said in a later post, contacting UPS customer service with a complaint was _the right thing to do_ and that's exactly what I did. You should know, though, that a signature WAS "required", yet the driver obviously ignored that requirement when he/she dropped off the expensive package at the wrong, vacant, house in a neighborhood known for items "disappearing" from front porches.
Or, maybe _you_ are only joking? Hard to tell with text.
ETA: It has started glitching again, no probes connected. See below. This is "minor" compared to how wild it can get.
Home
Help
Search
Login
Register
