DS1054z bug (with poll)

• DS1054z bug (with poll)
  Posted by Anand on 21 May, 2015 21:36
• 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

  ---

  
• #1 Reply
  Posted by kwass on 21 May, 2015 22:16
• Quote from: Anand on 21 May, 2015 21:36

  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.
  
• #2 Reply
  Posted by Anand on 21 May, 2015 22:23
• Quote from: kwass on 21 May, 2015 22:16

  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.
  
  

  Quote from: kwass on 21 May, 2015 22:16

  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.
• #3 Reply
  Posted by DanielS on 22 May, 2015 01:22
• 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.
• #4 Reply
  Posted by miguelvp on 22 May, 2015 01:48
• Too bad the poll doesn't have a I don't own a DS1054z so we can look at the results.
  
• #5 Reply
  Posted by alsetalokin4017 on 22 May, 2015 02:49
• Yep,  mine does that too. (firmware 04.02.SP4)
  
  I wonder if "unhacked" scopes do it.
• #6 Reply
  Posted by kedwards22 on 22 May, 2015 06:10
• I've got a brand new un-hacked scope (still using the trial time) and it has the bug.
• #7 Reply
  Posted by Anand on 22 May, 2015 07:22
• Quote from: miguelvp on 22 May, 2015 01:48

  Too bad the poll doesn't have a I don't own a DS1054z so we can look at the results.
  
  

  Fixed.
• #8 Reply
  Posted by dom0 on 22 May, 2015 09:34
• Quote from: evb149 on 22 May, 2015 02:54

  So the bug is that it shows the trigger point as preceding the displayed edge by a couple of hundred microseconds?
  

  
  Yep
• #9 Reply
  Posted by alsetalokin4017 on 22 May, 2015 15:55
• 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.
  
  

  ---

  

  
• #10 Reply
  Posted by alsetalokin4017 on 22 May, 2015 16:12
• In Horizontal Zoom mode it's even stranger.
  
  

  ---

  
• #11 Reply
  Posted by Jeroen3 on 26 May, 2015 18:12
• Confirmed in DS1104Z-S. Only in High-Res mode though.
  Could it be because 125MSa/s / 120 kpts = 1.04166666......?
• #12 Reply
  Posted by rolycat on 01 Jun, 2015 09:43
• Quote from: Anand on 22 May, 2015 07:22

  Quote from: miguelvp on 22 May, 2015 01:48

  Too bad the poll doesn't have a I don't own a DS1054z so we can look at the results.
  
  

  Fixed.
  

  
  Why not just click the "View Results" button below the poll?
  
• #13 Reply
  Posted by Psi on 01 Jun, 2015 10:26
• Its so specific that it could be a debug test that someone forgot to wrap with #ifdef debug
• #14 Reply
  Posted by jadew on 01 Jun, 2015 12:08
• I get this on the DS1104Z.
• #15 Reply
  Posted by alsetalokin4017 on 01 Jun, 2015 14:02
• Has anyone who is running the latest 1000 series firmware version 04.03 tried this test to see if the bug is still there?
• #16 Reply
  Posted by ebastler on 01 Jun, 2015 16:42
• Quote from: alsetalokin4017 on 01 Jun, 2015 14:02

  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.
• #17 Reply
  Posted by alsetalokin4017 on 01 Jun, 2015 16:49
• Quote from: ebastler on 01 Jun, 2015 16:42

  Quote from: alsetalokin4017 on 01 Jun, 2015 14:02

  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?
• #18 Reply
  Posted by ankerwolf on 23 Sep, 2015 09:08
• 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.

  ---

  

  

  
• #19 Reply
  Posted by Karel on 23 Sep, 2015 18:51
• Yep, same here with latest firmware.
  But only when one channel is switched on. When switching on multiple channels, the phenomena disappears.
• #20 Reply
  Posted by ankerwolf on 23 Sep, 2015 19:17
• Quote from: Karel on 23 Sep, 2015 18:51

  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)