Rigol DHO800/900 Oscilloscope Bug Reports + Firmware

[csuhi17]

Might actually be related to this finding: https://www.eevblog.com/forum/testgear/rigol-dho804-test-and-compare-thread/msg5112108/#msg5112108

My take on this is that the AWG module's high output level branch (THS3095) draws its power from (locally) unregulated rails. Since the analog frontends are pretty power intensive and the balance of this power may teeter between positive and negative rails, depending on the settings, the rails powering the AFE's local regulator(s) may very well fluctuate considerably. Rigol should have added local regulation to all AWG module supplies. Either greed, negligence or the lack of voltage headroom pushed them to do without those and voila.... At least, at low AWG level settings, the problem is absent.

I'm afraid of that too.
I would still understand, but I would not accept that this event occurs with a higher load on the AWG, but I connected the AWG->CHx with a BNC-BNC cable without load, and only 20mVpp 100kHz...

With the latest firmware, I noticed a bug that I don't know how I managed to cause.
On the left side of the trigger menu, where you select slope, all three rings were empty for me, none of them were selected.

The settings were set well, the channel I was watching was selected, and the trigger was also set to the Edge type.

it was resolved by choosing one of the three.

Unfortunately, I didn't take a picture of it.

[Howardlong]

I appreciate the excellent tip!  Mine was set to Default.  I changed it to Load Last, then changed all 4 probes to 10x, then restarted, and now I see it saves the 10x setting.  Great!  Thank you!

The first version of firmware for the DHO800/900 I couldn't even figure out how to change the probe attenuation!

It's this is still not a great solution IMHO because you usually don't want the probe config changing on a "default" button press either, which is a very common use case.

On a scope with no readback, or supplied without readback probes, going to "default" (either from boot or by pressing the button) should either not touch the probe config or set it to 10X. ISTR the same applies to Rigol's MSO5000. The solution in that case was that I have my own default setup config, including probe settings, and I use this rather than the scope's default button. (Other things I like is to have as my "default" are the trigger point at 10%, expand around trigger, and a Ch1 rising edge trigger at 1.5V).

As a comparison, the DS1000Z are at 10X after a default button press.

Even the Tek TDS 2024B I have here defaults to 10X (I can't remember the last time I turned it on, it was many years ago, but the clock is only 6.5 minutes out: the plastic's starting to get brittle though).

The Siglent SDS1000X-E & SDS2000X+ have a better way of implementing this with the Default button using a user-defined default, although even after a factory reset the channels are at 10X.

I am wondering if it's in response to "customer feedback", with noobs getting confused: I could certainly see that happening.

[norbert.kiszka]

As long as the scope remembers the settings when powered off, I don't see this as a problem.

It does NOT remember the change to 10x when you power off and then on again.  It resets to 1x, even if you do not press the AUTO button after restarting. Therefore, it is a problem that I would classify as a BUG.  But more than that, it's a huge headache to have to manually change all 4 channels to 10x every time you power on the scope!

I had same problem, but not anymore after firmware upgrade - sadly I dont remeber which one it was.

[Lathe26]

Bug: NTSC trigger is non-functional
[...]
I'm still willing to concede that the error could be occurring between the chair and the touchscreen, though it is looking unlikely.

I don't think this is a user error. Problems with video triggering have been reported months ago for the DHO1000, https://www.eevblog.com/forum/testgear/new-rigol-hdo1000-12-bit-dso-bugs/msg5007853/#msg5007853, and then for the DHO800 as well, https://www.eevblog.com/forum/testgear/rigol-dho800900-oscilloscope-bug-reports-firmware/msg5223633/#msg5223633. Looks like Rigol has not been able to fix this yet?

Good to know other folks have seen this as well, though mildly concerning the bug hasn't been addressed yet.  I missed the earlier post when I skimmed though all 13 pages of this thread last yesterday.

[calabr]

Found strange behavior - enabling LA dividing sample rate by 2, even in slow sampling
 I set 1ms/dev 100kpts - with 1 channel it's 6.25MSa/s with all 4 - the same 6.25MSa/s
 On the same ms/dev starting LA trace with or without any number of analog channels resulting in 3.125MSa/s and real captured data become 2x of buffer related to analog input buffer with same settings.
 Probable this behavior didn't allow to capture LA with max sample rate - 625MSa/s is max rate with LA.

  DHO924 software 00.01.02.00.02
 Steps to preproduce:
 1)  connect CH1 to 1kHz generator. Synchronize from CH1, set 100kpts, 1.00 ms/dev
   DHO set sample rate to 6.25MSps/s
   stop capturing.
max capture size is also halved to 25Mpts with LA enabled and still  25Mpts with LA+CH1
   switch view to 2ms/s - waveform zoom-out and graph only shown from -8ms to +8ms right and left is empty
2) switch back to 1.00 ms/dev, enable LA,
     start capturing - DHA show 3.125MSa/s
     stop capturing.
    switch view to 5ms/s - now graph is populated from -16ms to 16ms
 
 

[ebastler]

Found strange behavior - enabling LA dividing sample rate by 2, even in slow sampling

Unfortunately this is how the DHO900 behaves, by design: Enabling the logic analyser takes away half of the 1.25 GSa/s bandwidth. So for the analog channels, you only get 625/312/156 MSa/s, depending on how many analog channels you have enabled, once the logic analyser is activated.

It is an unusual (and unfortunate) aspect of the DHO900 design that the sampling rate is not limited by the ADC, but rather by the downstream data handling. And the digital data apparently have to go through that same bottleneck.

And yes, Rigol "forgot" to mention that in the datasheet. Disappointing.

[csuhi17]

Is there any explanation for why the memory is halved if LA is active?
Aren't those two extra memory chips for LA?

[Fungus]

Is there any explanation for why the memory is halved if LA is active?
Aren't those two extra memory chips for LA?

Nope. People have hacked DHO800 to enable the logic functions.

Those chips are a mystery...

[lunix]

I seem to be having a problem with the sensitivity of the touch screen not sensing my touch, any suggestions? I'm assuming this is capacitive, be nice if this had a mouse drive option.

I found that a mouse works with the DHO900, then afterward, I read that in the manual.  So I bought a larger touchscreen, and plugged it into the HDMI port, and into the USB on the front panel.  It works!  But then I wondered whether I could use a USB 2.0 hub to also allow me to use a USB flash drive simultaneously.  And, happily, that works too!

(if only the rest of the scope and logic analyzer worked as well)

[maxspb69]

Please check whether the SPI decoding works on logical channels with the latest firmware?
Previously, there were reports that SPI decoding only works on analog channels and doesn't work on digital ones.

[Howardlong]

Please check whether the SPI decoding works on logical channels with the latest firmware?
Previously, there were reports that SPI decoding only works on analog channels and doesn't work on digital ones.

That is absolutely the case on the DHO924 that I have on all firmware up to and including 1.02. Is there a newer version of firmware than 1.02 out there?

[Randy222]

Please check whether the SPI decoding works on logical channels with the latest firmware?
Previously, there were reports that SPI decoding only works on analog channels and doesn't work on digital ones.

That is absolutely the case on the DHO924 that I have on all firmware up to and including 1.02. Is there a newer version of firmware than 1.02 out there?

Need to be more specifc on FW vers.
There's a few flavors of "1.02"
00.01.02.00.00
00.01.02.00.01
00.01.02.00.02

[lunix]

They sent me 1.02.00.02

[tborgoyn]

SPI still not working correctly with LA channels in the latest 01.02.00.02 release. Below are the release notes for all of the versions.

[Model Supported] All the DHO800/900 series oscilloscopes
[Latest Revision Date] 2023/12/28

[Updated Contents]

v00.01.02.00.02  2023/12/28

1. Self calibration optimization update
2. Solve the problem that window transparency cannot load the last value
3. Solve the problem that the LA function cannot display the label after setting it


v00.01.02.00.01  2023/12/5

1. Self calibration optimization update
2. Solve edge jitter below 31kHz

v00.01.02.00.00  2023/11/2

1. Self calibration optimization update
2. Solve the problem of UltraLab startup connection failure
3. Solve the problem of failure to save waveform in wfm format
4. Solve the problem of unresponsive touch on startup screen

v00.01.01.00.02 2023/09/12

1. Self calibration optimization update
2. Update Help Documents

v00.01.01.00.01  2023/08/10

1. Remove all time-related displays on the instrument
2. To modify the vertical interface, click the wiring diagram to modify the AC coupling function
3. Modify the delayed scan Chinese display as Zoom
4. Modify the order of the menu in the upper right corner, put the measurement in the front and Default in the back
5. The probe ratio interface is removed, and the probe ratio option is added to the vertical first-level menu


v00.01.00.00.19  2023/07/24

1. The first version is released


-Released the production version.

[maxspb69]

Are you just drawing conclusions from this text? I read the release notes too, but the fact is that Rigol often corrects errors and does not mention them in the release notes. Therefore, it would be interesting if  the PLA2016 and DHO900 owner to check it  himself with the latest firmware 1.02.00.02

[simonboydfoley]

Hi guys,
         where can you get hold of the latest version of the firmware ?    The on on their website reads v00.01.01.00.01 in the release notes and my scope (DHO914S) came with version 00.01.02.
The logic Analyizer lable bug is driving me mad  .

[Randy222]

Hi guys,
         where can you get hold of the latest version of the firmware ?    The on on their website reads v00.01.01.00.01 in the release notes and my scope (DHO914S) came with version 00.01.02.
The logic Analyizer lable bug is driving me mad  .

The links, and/or FW attached, are throughout the posts, in this thread (I think) and in the DHO800/900 hacking thread.

[simonboydfoley]

Dohhhh    I must have been using an earlier 02 version ..... its finally fixed    this was driving my OCD mental ... read the post about different 02 versions and the penny dropped

[axantas]

Bug: NTSC trigger is non-functional
[...]
I'm still willing to concede that the error could be occurring between the chair and the touchscreen, though it is looking unlikely.

I don't think this is a user error. Problems with video triggering have been reported months ago for the DHO1000, https://www.eevblog.com/forum/testgear/new-rigol-hdo1000-12-bit-dso-bugs/msg5007853/#msg5007853, and then for the DHO800 as well, https://www.eevblog.com/forum/testgear/rigol-dho800900-oscilloscope-bug-reports-firmware/msg5223633/#msg5223633. Looks like Rigol has not been able to fix this yet?

Good to know other folks have seen this as well, though mildly concerning the bug hasn't been addressed yet.  I missed the earlier post when I skimmed though all 13 pages of this thread last yesterday.

If I my chime in as element between the chair and the touch screen. Trigger on analog TV-Signals on a DHO914 is not working. PAL here. It is not possible to trigger a clean, stable analog TV-Signal (from a digital source btw.) it works however, if you stop acquisition. But I prefer not to look at a single screenshot.
Most recent firmware, that I found on Rigols US-Server, because it it not available in Europe...

[Fungus]

If I my chime in as element between the chair and the touch screen. Trigger on analog TV-Signals on a DHO914 is not working. PAL here. It is not possible to trigger a clean, stable analog TV-Signal (from a digital source btw.) it works however, if you stop acquisition. But I prefer not to look at a single screenshot.

Sounds like trigger delay might help with that. Give it a try.

[maxspb69]

it works however, if you stop acquisition. But I prefer not to look at a single screenshot.

Please explain what you meant? What needs to be done to make the trigger execute once?

PS. If you need "Video" sync, then you can use "Sync by N-th pulse". It works great!

[axantas]

it works however, if you stop acquisition. But I prefer not to look at a single screenshot.

Please explain what you meant? What needs to be done to make the trigger execute once?

PS. If you need "Video" sync, then you can use "Sync by N-th pulse". It works great!

If you stop acquisition, you get the "screenshot" of that moment, and a clear signal, not what you usually want to see from a continuous signal  .

But: The Sync on Pulse 64Microseconds syncs on one line - question is which one... but it works somehow.

Triggering on Video (line) just looks like it tries to do it on at least two different lines, clearly failing to do that properly at the same time.

"Trigger delay" refers to two channels - which I do not have as a reference.

I do have the impression, that manually adjusting the Trigger in Video, that "knob" just does nothing, you never see the "T'D" - triggered - message, while in Sync on Pulse, you can adjust that.
It is not a very important function, but nevertheless strange, they obviously do not care at RIGOL.

[maxspb69]

It is not a very important function, but nevertheless strange, they obviously do not care at RIGOL.

Today, few people work with analog video signals. So there were probably few complaints to Rigol about this issue.

There are much more significant and serious errors in the firmware, but Rigol doesn’t care either 

[Fungus]

If you stop acquisition, you get the "screenshot" of that moment, and a clear signal

So it is basically working...

It is not a very important function, but nevertheless strange, they obviously do not care at RIGOL.

Today, few people work with analog video signals. So there were probably few complaints to Rigol about this issue.

And most of those people probably already have an oscilloscope that can do it.

[Fungus]

I do have the impression, that manually adjusting the Trigger in Video, that "knob" just does nothing, you never see the "T'D" - triggered - message, while in Sync on Pulse, you can adjust that.

Just a thought: Do you have your probe attenuation set to 1x or 10x?