New Rigol DS1054Z oscilloscope

[technogeeky]

So I decided it would be very ungentlemanly for me to withhold teardown information from my (apparently uniquely version-ed) 0.14 board. So I tried to avoid destroying my VOID IF BROKEN sticker and failed miserably. Having passed that barrier, I didn't see any reason to not go ahead.

Please excuse the blurry pictures. These were taken from a low-Neptune orbit space telescope, so they are actually quite well focused despite being apparently blurry.




































So, after all that... what's changed? As far as I can tell, nothing.


The only real change is that the logic analyser pinout grid has been removed, and some associated hardware has been removed. The memory is a different chip. The pin connectors under 'SP Version' have been removed. As far as I can tell, nothing has been added or changed.

I suppose I was naive to have thought anything else would happen.

Oh well. I hope I don't need to warranty this thing, ever.

Cheers,
-tg

[alsetalokin4017]

And yet, you seem to be critical of those of us who have applied that update and are not happy with the problems it introduces.

I'm only critical of people of the people who invade every single thread that mentions the DS1054Z and try to turn it into their own personal Rigol-bashing thread.

eg. The "DS1054Z noise" thread that you recently invaded.

Rigol-bashing? Moi? Surely you jest. I use the scope every day in my work and I've helped many people understand the scope's quirks and limitations. It gives me great amusement. And I've never once complained about the "loud" fan or the fumbly encoders.

After all, what other scope can display 5 bugs simultaneously?  And for only 400 dollars, even.     

When are you going to update your scope to the latest firmware, so that you can have as much fun with it as the rest of us?

[alsetalokin4017]

@ technogeeky:

So what's up with this transistor?

[Fungus]

Rigol-bashing? Moi? Surely you jest. I use the scope every day in my work and I've helped many people understand the scope's quirks and limitations. It gives me great amusement. And I've never once complained about the "loud" fan

That's because you work in a noisy room.

https://www.eevblog.com/forum/testgear/rigol-ds1054z-ds1000z-fan-noise/msg649480/#msg649480

When are you going to update your scope to the latest firmware, so that you can have as much fun with it as the rest of us?

Is the "latest" firmware available to the public yet?

[technogeeky]

@ technogeeky:

So what's up with this transistor?

Unfortunately, I had to re-open it to find out.

Fortunately, it was just some flux or glue or something that made the transistor shiny. It's intact. (Which is what I expected, since all four channels work fine and look OK).

Whew!

[alsetalokin4017]

Rigol-bashing? Moi? Surely you jest. I use the scope every day in my work and I've helped many people understand the scope's quirks and limitations. It gives me great amusement. And I've never once complained about the "loud" fan

That's because you work in a noisy room.

Yes, "work" being the operative word.  And I also know how to press the encoder shaft-buttons so as not to turn them at the same time -- something that seems to be beyond the ability of some users, who have even gone so far as to tear their scopes apart to replace the encoders.

https://www.eevblog.com/forum/testgear/rigol-ds1054z-ds1000z-fan-noise/msg649480/#msg649480

When are you going to update your scope to the latest firmware, so that you can have as much fun with it as the rest of us?

Is the "latest" firmware available to the public yet?

The latest firmware has been available to the public since last October or earlier, and its .GEL file is dated 11 September 2015. 

Although one source says it is dated June 16, 2015.

http://beyondmeasure.rigoltech.com/acton/form/1579/001e:d-0001/0/-/-/-/-/index.htm

But then, you knew that already.

[MarkF]

When are you going to update your scope to the latest firmware, so that you can have as much fun with it as the rest of us?

Is the "latest" firmware available to the public yet?

For me, I have NO intention of ever updating my firmware to 00.04.03.SP2.  I'm holding out for the next version to see what it has to offer.  I'm currently running 00.04.03.SP1.

[metrologist]

And I also know how to press the encoder shaft-buttons so as not to turn them at the same time -- something that seems to be beyond the ability of some users, who have even gone so far as to tear their scopes apart to replace the encoders.

I'm really sorry I mentioned this as a minor annoyance. It was a stretch...

[bitseeker]

No need to be sorry for being annoyed by that "feature". Rigol should've used a rotary encoder with detents for the menu. A smooth one is suboptimal for this purpose.

[JPortici]

The latest firmware

please, can you two at least agree on a truce until the NEW firmware update is released? (rumors say it is being released later this month)

[Fungus]

No need to be sorry for being annoyed by that "feature". Rigol should've used a rotary encoder with detents for the menu. A smooth one is suboptimal for this purpose.

They should allow you to press the menu button to accept the selection and close the menu (the same button that opened the menu).

Also: Using the blue up/down arrows to go up/down inside the menu would be a nice touch.

[bitseeker]

I agree that there are many interaction design flaws with the interface in its current form.

[tooki]

And I also know how to press the encoder shaft-buttons so as not to turn them at the same time -- something that seems to be beyond the ability of some users, who have even gone so far as to tear their scopes apart to replace the encoders.

Good usability shouldn't require the user to learn a fiddly method just to perform an everyday function. Rigol screwed the pooch on this. A non-detended encoder without software hysteresis is just terrible.

[ProBang2]

Occurs the problem with the multipurpose encoder after some time of using?
Or just on day one?

Honest: I have no problem with it (at least until now).   
Even if a detent button would have been nicer...

[rstofer]

Occurs the problem with the multipurpose encoder after some time of using?
Or just on day one?

Honest: I have no problem with it (at least until now).   
Even if a detent button would have been nicer...

It's a design flaw and the effect is immediately apparent.  Just about the time you press the knob, the selection changes.  Sure, it is possible to 'get along' with the encoder but why?  Replacing the encoder is pretty easy and the improvement is noticeable.

As to the warranty?  Who cares?

[JPortici]

never had this particular problem.
though i would love if they corrected the sensitivity for the horizontal position knob
i don't know if it is only mine but there is a very tiny difference in rotating speed between moving a couple of pixels and a whole couple screens

[JohnPen]

I tried to duplicate your problem just using the calibration square wave.  I found small slow speed adjustments worked fine in pixel terms.  A quick tweek does make it shift in larger steps.  It does depend on how your triggering is set up and the type of waveform you are displaying.  A similar effect shows up with a sine wave display.  Perhaps you can supply the set up you are using?   I have not found it a problem on my scope.

John

[boba]

Just a comment that the all-options hack still works fine on a new scope delivered only last week, v4.03.SP2. I had a couple of false starts, but the archived site at https://web.archive.org/web/20131215225141/http://riglol.3owl.com/ worked just fine for me. I used UltraSigma to avoid mistakes and typos.

[janekivi]

After little pause with 3des in Siglent firmware I took a small look in Keysight nk.bin file and
don't remember where after that... But then I start peeking into Rigol DS1000ZUpdate.GEL.
This is simple and of course there is keygenerator for software options...
I can't disassemble something but just looking this "pluses" part here.
Update file itself is header with file names - their lenght - data beginning in file - and crc32.
Last file in this row is end part with only start and lenght. After extracting files some of them
have header with crc32 and some data like:
1B C3 C1 96 03 00 00 00 FC A7 10 00 AA 55 55 AA FB 7E 3D 00 00 00 00 00
and after that is magic bytes for LZMA compression which are 5D 00 00 80. So after striping
previous header this file can be unpacked with 7zip and then ... whatever you like

[bitseeker]

Hi janekivi! Thanks for exploring this. I saw your dissecting work on the Siglent thread. So, we can fix those errant strings and reassemble the .GEL file? That'd be great. I'd like to fix some of the other labels, messages, etc.

[janekivi]

Yeah, but there is 260 bytes footer which can contain something... not hackable with notepad.
There may be 256 bytes some crypted data.
Main app can handle:
40150D70: found sparse constants for RC5_RC6
401CEDDC: found sparse constants for SHA-1
401F3DEC: found const array CRC32_m_tab (used in CRC32)
401F5E6C: found const array zinflate_lengthExtraBits (used in zlib)
401F5EE0: found const array zinflate_distanceExtraBits (used in zlib)
Somebody must look how app is reading that part of firmware file.
There is 2 files for screen gui - guiPicData.hex and guiResData.hex (inside here is lots of text).

[janekivi]

Main app is too big, over 1000kb when packed. It contains many stuff...
like internal web pages and images

[bitseeker]

Thanks for the attachments. I'll take a closer look at them tonight.

[bitseeker]

guiPicData, as the name suggests, appears to be image data (icons, etc.). guiResData has a lot of text resources including the help text and menu item labels. I wasn't able to find "Pluses", only the normal "Pulse" and "Pulses". I was also looking for "Function Limited!", but didn't find it in guiResData. Perhaps those labels and messages are in a different file.

Where did you find "Pluses" when you made the screenshot?

[smithnerd]

I had a poke around in there last night too. Almost everything of interest is in SparrowAPP.out.

Code: [Select]

$ strings SparrowAPP.out | grep -i -e limited\! -e pluses
+Pluses
-Pluses
Function Limited!
Parameter Limited!
Interesting:

Code: [Select]

$ strings SparrowApp.out | grep -i version
Version:
A newer software version detected.
An older software version detected.
The same software version detected.