DS1054z bug (with poll) - Page 1
Forum section: electronics / testgear

author: Anand
author_rank: Contributor
timestamp: May 21, 2015, 09:36:26 pm
content: Input signal: probe compensation 1kHz square wave from the scopeTrigger: DC / CH1 / 1.5VAquisition:High Res/120kmem. depthHorizontal position:0psHorizontal scale:50us/divI get the attached pic.Firmware version: 4.03 and the bug was present on 4.02.SP4

author: kwass
author_rank: Frequent Contributor
timestamp: May 21, 2015, 10:16:54 pm
content: Quote from: Anand on May 21, 2015, 09:36:26 pmGood 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.

author: Anand
author_rank: Contributor
timestamp: May 21, 2015, 10:23:43 pm
content: Quote from: kwass on May 21, 2015, 10:16:54 pmWell, I've got another bug, that dissapears when High Res is on. I'll post that soon, too.Quote from: kwass on May 21, 2015, 10:16:54 pmSweet, 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.

author: DanielS
author_rank: Frequent Contributor
timestamp: May 22, 2015, 01:22:33 am
content: 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.

author: miguelvp
author_rank: Super Contributor
timestamp: May 22, 2015, 01:48:33 am
content: Too bad the poll doesn't have a I don't own a DS1054z so we can look at the results.

author: alsetalokin4017
author_rank: Super Contributor
timestamp: May 22, 2015, 02:49:47 am
content: Yep, mine does that too. (firmware 04.02.SP4)I wonder if "unhacked" scopes do it.

author: kedwards22
author_rank: Newbie
timestamp: May 22, 2015, 06:10:06 am
content: I've got a brand new un-hacked scope (still using the trial time) and it has the bug.

author: Anand
author_rank: Contributor
timestamp: May 22, 2015, 07:22:38 am
content: Quote from: miguelvp on May 22, 2015, 01:48:33 amFixed.

author: dom0
author_rank: Super Contributor
timestamp: May 22, 2015, 09:34:13 am
content: Quote from: evb149 on May 22, 2015, 02:54:53 amYep

author: alsetalokin4017
author_rank: Super Contributor
timestamp: May 22, 2015, 03:55:30 pm
content: 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.

author: alsetalokin4017
author_rank: Super Contributor
timestamp: May 22, 2015, 04:12:52 pm
content: In Horizontal Zoom mode it's even stranger.

author: Jeroen3
author_rank: Super Contributor
timestamp: May 26, 2015, 06:12:32 pm
content: Confirmed in DS1104Z-S. Only in High-Res mode though.Could it be because 125MSa/s / 120 kpts = 1.04166666......?

author: rolycat
author_rank: Super Contributor
timestamp: June 01, 2015, 09:43:51 am
content: Quote from: Anand on May 22, 2015, 07:22:38 amWhy not just click the "View Results" button below the poll?

author: Psi
author_rank: Super Contributor
timestamp: June 01, 2015, 10:26:33 am
content: Its so specific that it could be a debug test that someone forgot to wrap with #ifdef debug

author: jadew
author_rank: Frequent Contributor
timestamp: June 01, 2015, 12:08:39 pm
content: I get this on the DS1104Z.

author: alsetalokin4017
author_rank: Super Contributor
timestamp: June 01, 2015, 02:02:58 pm
content: Has anyone who is running the latest 1000 series firmware version 04.03 tried this test to see if the bug is still there?

author: ebastler
author_rank: Super Contributor
timestamp: June 01, 2015, 04:42:35 pm
content: Quote from: alsetalokin4017 on June 01, 2015, 02:02:58 pmWell, according to the poll above, 3 people have tried it and have all reproduced the error.

author: alsetalokin4017
author_rank: Super Contributor
timestamp: June 01, 2015, 04:49:50 pm
content: Quote from: ebastler on June 01, 2015, 04:42:35 pmDuh... insert embarrassed smiley here ... Thanks....Does anyone know what the 04.03 firmware actually _does_ fix (or change) then?

author: ankerwolf
author_rank: Regular Contributor
timestamp: September 23, 2015, 09:08:03 am
content: Hello,it is a very special bug!I can reproduce also in Version 00.04.03.SP1BUTONLYat 120kpts & H=50µsANDdepends on the position of T !!!See attached pictures.

author: Karel
author_rank: Super Contributor
timestamp: September 23, 2015, 06:51:19 pm
content: Yep, same here with latest firmware.But only when one channel is switched on. When switching on multiple channels, the phenomena disappears.

author: ankerwolf
author_rank: Regular Contributor
timestamp: September 23, 2015, 07:17:45 pm
content: Quote from: Karel on September 23, 2015, 06:51:19 pmThat is right, because of the Mem.Depth is NOT 120k !(And the bug ist only at 120k pts)