EEVblog Electronics Community Forum
Products => Test Equipment => Topic started by: Anand on May 21, 2015, 09:36:26 pm
-
Input signal: probe compensation 1kHz square wave from the scope
Trigger: DC / CH1 / 1.5V
Aquisition: High Res / 120k mem. depth
Horizontal position: 0ps
Horizontal scale: 50us/div
I get the attached pic.
Firmware version: 4.03 and the bug was present on 4.02.SP4
-
Input signal: probe compensation 1kHz square wave from the scope
Trigger: DC / CH1 / 1.5V
Aquisition: High Res / 120k mem. depth
Horizontal position: 0ps
Horizontal scale: 50us/div
I get the attached pic.
Firmware version: 4.03 and the bug was present on 4.02.SP4
Good find, but weird how it has to be exactly those setting on the Aquire menu to see this. IIRC people of this forum found that High Res mode was useless, so this is yet another reason to never use it. I've added this to the bug list thread.
-
Good find, but weird how it has to be exactly those setting on the Aquire menu to see this. IIRC people of this forum found that High Res mode was useless, so this is yet another reason to never use it.
Well, I've got another bug, that dissapears when High Res is on. I'll post that soon, too.
I've added this to the bug list thread.
Sweet, thanks, I've wanted to do it myself but I didn't know if it was just me experiencing this bug so... I asked around first. :D
-
That's a strangely specific bug.
And yes, I got that on my 1054Z too.
This is a strangely specific bug. It works on any channel when the same channel is used as the trigger source and only one channel is enabled at a time.
I probably would never have come across this bug on my own since I practically always use at least two channels and usually limit memory depth to 30-60k points when I save waveforms.
-
Too bad the poll doesn't have a I don't own a DS1054z so we can look at the results.
-
Yep, mine does that too. (firmware 04.02.SP4)
I wonder if "unhacked" scopes do it.
-
I've got a brand new un-hacked scope (still using the trial time) and it has the bug.
-
Too bad the poll doesn't have a I don't own a DS1054z so we can look at the results.
Fixed. :D
-
So the bug is that it shows the trigger point as preceding the displayed edge by a couple of hundred microseconds?
Yep
-
Seventy-five microseconds, actually, IF your horizontal trigger position is on the center graticule marker. Less if the trigger position is to the left, more if it is to the right of center. Seems weird that the error should depend on the screen Horizontal Position that way.
And it does it on Trailing Edge and Both Edges trigger slope settings as well.
-
In Horizontal Zoom mode it's even stranger.
-
Confirmed in DS1104Z-S. Only in High-Res mode though.
Could it be because 125MSa/s / 120 kpts = 1.04166666......?
-
Too bad the poll doesn't have a I don't own a DS1054z so we can look at the results.
Fixed. :D
Why not just click the "View Results" button below the poll?
-
Its so specific that it could be a debug test that someone forgot to wrap with #ifdef debug
-
I get this on the DS1104Z.
-
Has anyone who is running the latest 1000 series firmware version 04.03 tried this test to see if the bug is still there?
-
Has anyone who is running the latest 1000 series firmware version 04.03 tried this test to see if the bug is still there?
Well, according to the poll above, 3 people have tried it and have all reproduced the error.
-
Has anyone who is running the latest 1000 series firmware version 04.03 tried this test to see if the bug is still there?
Well, according to the poll above, 3 people have tried it and have all reproduced the error.
Duh... insert embarrassed smiley here ... Thanks....
Does anyone know what the 04.03 firmware actually _does_ fix (or change) then?
-
Hello,
it is a very special bug!
I can reproduce also in Version 00.04.03.SP1
BUT
ONLY at 120kpts & H=50µs
AND depends on the position of T !!!
See attached pictures.
-
Yep, same here with latest firmware.
But only when one channel is switched on. When switching on multiple channels, the phenomena disappears.
-
But only when one channel is switched on. When switching on multiple channels, the phenomena disappears.
That is right, because of the Mem.Depth is NOT 120k !
(And the bug ist only at 120k pts)