New Rigol DS1054Z oscilloscope

[quetzalcoatl]

I'm running v00.04.04.SP1 which should be the latest (Brand new scope, was updated and dispatched by Telonic on Tuesday) on board version 0.1.4 and haven't seen any lock-ups or reboots - Not that I've been using it for very long.

This version is listed as the latest as of the 24th of Oct, so might want to try this:
http://www.rigol-uk.co.uk/Get-the-latest-RIGOL-firmware-p/firmtest.htm

Unfortunately, it's just a list with no download.
Like IAmBack said, links for ds1000z vanished from official download site.
Link from RoGeorge to beyond measure points to fw image from 2016/09/14 ver. v00.04.04.01.01.
IIRC that one had a short name of 04.04.SP1

But maybe your device is really ahead
Could you check (quickly press menu-menu-force-menu on trigger button group, and then go to info panel) and then check what's the full version number?

[yngndrw]

Sorry, didn't realise that was just a short name.

Full version number is: v00.04.04.01.01

Board version: 0.1.4
Boot version: 0.0.1.4
Firmware version: 0.2.3.1.1
CPLD version: 1.1
Build date: Aug 23 2016

[bitseeker]

Anyone running the current v00.04.04.01.01  2016/09/14 firmware?  I updated today from an older 4.03...something and now I get random reboots and lockups.

I'm running the current firmware version. No lockups. If you haven't already, be sure to run the self-calibration after installing a new firmware version.

[JohnPen]

I have been running the latest build for over a month with no problems.

S/W Version 00.04.04.01.01
Board Version 0.1.1
Boot  0.0.1.2
F/W Version 0.2.3.11
CPLD 1.1

Build date Aug 23rd 2016

Perhaps a second attempt on Self Calibration may help.

[Fungus]

Anyone running the current v00.04.04.01.01  2016/09/14 firmware?

Lots of people, including me.

I updated today from an older 4.03...something and now I get random reboots and lockups.

Sounds like something went very wrong in the update. Try doing it again.

[ebastler]

Like IAmBack said, links for ds1000z vanished from official download site.
Link from RoGeorge to beyond measure points to fw image from 2016/09/14 ver. v00.04.04.01.01.
IIRC that one had a short name of 04.04.SP1

Indeed, no DS1000Z firmware here either: http://int.rigol.com/Support/SoftDownload/3

I notice that Rigol seem to have changed their tagline (logo in the upper left corner of that page) to "Innovation or nothing". So I guess it's "nothing" for us DS1000Z users for the moment...   

[MarkF]

The  latest firmware and release notes for the DS1000Z can be found at http://beyondmeasure.rigoltech.com/acton/fs/blocks/showLandingPage/a/1579/p/p-0019/t/page/fm/0

[canibalimao]

Is it a reliable source?

[metrologist]

it's the manufacture's site.

[ebastler]

The  latest firmware and release notes for the DS1000Z can be found at http://beyondmeasure.rigoltech.com/acton/fs/blocks/showLandingPage/a/1579/p/p-0019/t/page/fm/0

Ah, thanks -- that's the page I recalled, but had not bookmarked.
Heck, how many different domains does Rigol operate?! And are the "beyond measure" or for "innovation or nothing?" 

[uvamosk]

Hey Guys,
 I just got my Ds1054z today, it was built in August.
It Came as follows
 Software Version: 00.04.03.SP2
 Board Version: 0.1.4

Just did firmware update with no issues.
I tried to replicate the 5us Jitter issues and it didn't really seem to show up or I can't see in good enough detail.

 I did just like Dave and them on the youtube videos was doing and I don't see much of a difference at all. Maybe a faint amount, but better than what Dave had on his videos.

Just a FYI.

[Fungus]

I tried to replicate the 5us Jitter issues and it didn't really seem to show up

Dave did a follow-up video showing it was fixed about a year ago.

[uvamosk]

I tried to replicate the 5us Jitter issues and it didn't really seem to show up

Dave did a follow-up video showing it was fixed about a year ago.

 Yeah I saw his video, but here is the funny thing, I did the test for jitters before I did frimware update and it was better than his after the fix. After the firmware update, it looks worse  LOL. I went from 04.03 to 04.04
 To bad you can't downgrade. BTW, instead of it being blurry like his was mine is more of just a bunch of ghost jitters, very very faint. Looks like one of those electrostatic spheres. If I go to 24m Depth it goes away completely

[Fungus]

Yeah I saw his video, but here is the funny thing, I did the test for jitters before I did frimware update and it was better than his after the fix. After the firmware update, it looks worse  LOL. I went from 04.03 to 04.04

I think it was fixed in version 04.02

[uvamosk]

Yeah I saw his video, but here is the funny thing, I did the test for jitters before I did frimware update and it was better than his after the fix. After the firmware update, it looks worse  LOL. I went from 04.03 to 04.04

I think it was fixed in version 04.02

 I was reading through their notes and saw that so even more the mystery. I did the calibration after I did the firm ware update but I don't think that would have cause it to get worse. I would be nice if I could downgrade it and see if it goes away like it was when I took it out of the box. Though it's not a big issue at this time as it's my first scope and for what I'm using it for now I won't even notice it. Though it does suck though, that it worked better out of the box than after the update lol.

[uvamosk]

Just for your amusement.
One is with zero
the other was out 25us

 Interesting how this wasn't doing it before I did update and calibration.

 

[David Hess]

Since Rigol missed the problem for months and then released a bunch of different fixes for the sampling jitter problem and they only improved some but not all instruments, I have always been dubious that it was fixed for all instruments.

Is there any possibility that the jitter is from your signal source?  I guess not if it changed when the firmware changed.

[alsetalokin4017]

How's this?
Signal source is a MTron MTO-T1-S3 oscillator chip at 1.000000 MHz (CH1) connected by normal 10x probe to channel input.
CH2 is the output from the "trigger out" BNC connector on the rear of the instrument, connected by a 50 ohm BNC patchcord and 50 ohm thru-terminator at the channel input.

[David Hess]

How's this?
Signal source is a MTron MTO-T1-S3 oscillator chip at 1.000000 MHz (CH1) connected by normal 10x probe to channel input.
CH2 is the output from the "trigger out" BNC connector on the rear of the instrument, connected by a 50 ohm BNC patchcord and 50 ohm thru-terminator at the channel input.

It looks fine but the sampling jitter delay problem manifested at much longer delays, like multiples of 5 microseconds when the PLL clock source was 200 kHz, and the trigger output has delay and jitter by design; it is more like a count output.

[pascal_sweden]

Does this mean that "Yaigol" is back?

[uvamosk]

Since Rigol missed the problem for months and then released a bunch of different fixes for the sampling jitter problem and they only improved some but not all instruments, I have always been dubious that it was fixed for all instruments.

Is there any possibility that the jitter is from your signal source?  I guess not if it changed when the firmware changed.

 I thought it might be something with source but it goes away when I set it to 0 so I can't see it being source since it only shows up at the 5us intervals. The other thing is once I move the trigger over past 5us it shows up and then wont go away till I zero the trigger again, Even if I get off the 5us intervals. I just cant figure out why out of the box with the updates that fixed jitters already installed it was fine then got worse after the latest firmware.. hmm

[2N3055]

I tried it and found out two interesting things.. First, I was able to replicate it with my Hameg HM8030-6... And jitter was proportional with delay, and wasn't multiple of 5 or something... Just more delay, more jitter... 

Then I switched to DG1032Z, with low jitter oscillator... And didn't see anything anymore...
So definitely a bit of frequency modulation there....

But, with DG1032Z,  if I put delay to something like 200 milliseconds and watched signal at 5 ns/DIV, there it was again...

And it got me thinking.. If you trigger now, and wait let's say  200 msec it's 2000000 periods of 10MHz.. and 5ns jitter on 200msec is 250ppb ...

And then I did autocal again.. And now it is less than 2-3 ns at 200 msec, so that would be  100-150ppb....



In specification for DS1074Z I couldn't find jitter spec..  DG1032Z is specced at 200ps at 10 MHz..

[David Hess]

Since Rigol missed the problem for months and then released a bunch of different fixes for the sampling jitter problem and they only improved some but not all instruments, I have always been dubious that it was fixed for all instruments.

Is there any possibility that the jitter is from your signal source?  I guess not if it changed when the firmware changed.

I thought it might be something with source but it goes away when I set it to 0 so I can't see it being source since it only shows up at the 5us intervals. The other thing is once I move the trigger over past 5us it shows up and then wont go away till I zero the trigger again, Even if I get off the 5us intervals. I just cant figure out why out of the box with the updates that fixed jitters already installed it was fine then got worse after the latest firmware.. hmm

With the delay set to 0, the trigger follows any jitter whether inside or outside of the oscilloscope so there is nothing to display.

The original problem was that the PLL filter was not implemented correctly and Rigol managed to fix it, or sort of fix it, by updating the firmware to adjust the PLL settings.  Since the PLL reference frequency was 200 kHz, the PLL was producing sidebands at 200 kHz and the jitter was maximum every 5uS, 15uS, 25us, etc. from the trigger point.

Since your oscilloscope is new, it might just be broken.  What about returning it as a warranty claim?

[uvamosk]

Since Rigol missed the problem for months and then released a bunch of different fixes for the sampling jitter problem and they only improved some but not all instruments, I have always been dubious that it was fixed for all instruments.

Is there any possibility that the jitter is from your signal source?  I guess not if it changed when the firmware changed.

I thought it might be something with source but it goes away when I set it to 0 so I can't see it being source since it only shows up at the 5us intervals. The other thing is once I move the trigger over past 5us it shows up and then wont go away till I zero the trigger again, Even if I get off the 5us intervals. I just cant figure out why out of the box with the updates that fixed jitters already installed it was fine then got worse after the latest firmware.. hmm

With the delay set to 0, the trigger follows any jitter whether inside or outside of the oscilloscope so there is nothing to display.

The original problem was that the PLL filter was not implemented correctly and Rigol managed to fix it, or sort of fix it, by updating the firmware to adjust the PLL settings.  Since the PLL reference frequency was 200 kHz, the PLL was producing sidebands at 200 kHz and the jitter was maximum every 5uS, 15uS, 25us, etc. from the trigger point.

Since your oscilloscope is new, it might just be broken.  What about returning it as a warranty claim?

 Well thats what I am thinking but, I ran the hack on it since it was working just fine before the update. Unless there is a way to uninstall the hack.

[rolycat]

Since your oscilloscope is new, it might just be broken.  What about returning it as a warranty claim?

 Well thats what I am thinking but, I ran the hack on it since it was working just fine before the update. Unless there is a way to uninstall the hack.

There is.  As has been detailed many times, you can revert it to a vanilla 50Mhz model by connecting an ethernet cable and telnetting in on port 5555. Then use the SCPI command:

:SYSTem:OPTion:UNINSTall

alsetalokin4017 provided a detailed step-by-step description of the process here.

I will add a link to that post in the FAQ section at the start of this thread.