Siglent SDS2000X Plus

[Svrbinek]

Quick update: I tried the “3× factory defaults in a row” (Factory Default → reboot → Factory Default → reboot → Factory Default → reboot) and unfortunately it made no difference.
I also reinstalled the OS/firmware again (fresh upgrade), still the same.
After every reboot a new log file is created and it always contains the same errors (see logs 1–3).
Current boot time is about 70 seconds.
The scope otherwise works normally once it’s up, but during boot it clearly doesn’t like something / fails to load something (based on the repeated log errors).
Any further ideas what could be causing this and how to fix it (ideally without touching calibration data)?

[2N3055]

Quick update: I tried the “3× factory defaults in a row” (Factory Default → reboot → Factory Default → reboot → Factory Default → reboot) and unfortunately it made no difference.
I also reinstalled the OS/firmware again (fresh upgrade), still the same.
After every reboot a new log file is created and it always contains the same errors (see logs 1–3).
Current boot time is about 70 seconds.
The scope otherwise works normally once it’s up, but during boot it clearly doesn’t like something / fails to load something (based on the repeated log errors).
Any further ideas what could be causing this and how to fix it (ideally without touching calibration data)?

I see no errors in those logs that are problematic.
There is nothing suspicious in that log. "cfg_limit_data_xml.cpp" are normal. And they are all gone in few ms.
I see no delays there..

I see all this FW reloads, resets, but first question was never asked: what IS normal boot time other users have with same FW.
So you know if simply last FW is longer to load and there is no problem.

I don't have that scope but others that do might chime in what exactly boot time is on the latest FW.

None of my scopes boot for less than a minute, including Keysight 3000T that is more than minute and a half. Except SDS800xHD that boots in cca 44seconds, but that is simpler scope with much faster processor.
As firmware is updated and new functions are added, it is not unusual for the scope to boot longer, if it has more new stuff to load..  70 seconds is faster than SDS2000xHD, for instance, that boots in cca 90 sec...

So my advice would be to ask other users if they will be so kind to share how long it takes for their scopes to boot to establish baseline, to establish what is normal for that FW version. Only if your boot time largely differs from other people scopes then there might something wrong.

[mawyatt]

So my advice would be to ask other users if they will be so kind to share how long it takes for their scopes to boot to establish baseline, to establish what is normal for that FW version. Only if your boot time largely differs from other people scopes then there might something wrong.

Ours takes ~60 seconds to boot with version 1.6.2

Best

[FiveFiveFive]

Mine (with all 'enhancements' enabled) takes about 55 seconds to the normal graticule display, about 70 seconds until it triggers and starts displaying a trace. Software is 1.6.2r5 with OS 5.4.0.

[Peter_O]

1:08 with 1.6.2 and 5.4.0

[Johnny B Good]

Mine is currently still on Version 1.3.7R5 and takes 52 seconds to boot up (to display the traces) versus the original 46 seconds boot time when I bought it ~ 4 years ago.  What was worse was the fact that it consumed 54W versus the 22W of the SDS1202X-E which boots in a mere 16 seconds.

 It was those annoyances that caused me to carry on using the SDS1202X-E, saving the SDS2000X Plus  for those rare occasions whenever the need justified the expense in electricity costs and the extra half minute boot time.

 However, my needs changed about two years ago and it's now the SDS1202X-E which very rarely gets fired up. Unlike the case with the SDS1202X-E where I could afford to leave it powered up 24/7 for months at a time, the SDS2000X Plus gets shut down overnight - I've come to terms with its long boot time by virtue of only having to suffer this once a day and accept the higher energy consumption as simply the price of ownership of a higher spec 'scope.

[Svrbinek]

Thanks everyone for the replies — much appreciated.
It looks like my boot time is actually in line with what you reported: ~55 s to the graticule and ~70 s until it starts triggering/drawing traces (FW 1.6.2R5, OS 5.4.0, “full/enhancements” enabled). So it’s probably normal and not a fault.

Just for peace of mind: could someone with the same FW/OS check the Developer/Debug log right after boot and confirm whether you also see those recurring messages (the cfg_limit_data_xml.cpp ... load limit xml failed lines / draw-wave-thread timeout)? I’m mainly trying to confirm my logs look the same as other units.
(I can access the Developer/Debug menu; if you prefer not to post the password publicly, a PM is fine.)

Thanks again!

[2N3055]

Thanks everyone for the replies — much appreciated.
It looks like my boot time is actually in line with what you reported: ~55 s to the graticule and ~70 s until it starts triggering/drawing traces (FW 1.6.2R5, OS 5.4.0, “full/enhancements” enabled). So it’s probably normal and not a fault.

Just for peace of mind: could someone with the same FW/OS check the Developer/Debug log right after boot and confirm whether you also see those recurring messages (the cfg_limit_data_xml.cpp ... load limit xml failed lines / draw-wave-thread timeout)? I’m mainly trying to confirm my logs look the same as other units.
(I can access the Developer/Debug menu; if you prefer not to post the password publicly, a PM is fine.)

Thanks again!

I already told you that "cfg_limit_data_xml.cpp" entries are normal. They are seen in other touch scopes by Siglent too. Why, beats me.. It looks weird, but is not any kind of problem.
Your scope is fine.

[tautech]

This seemed like a faulty scope but it wasn't.....



Instead the incorrect waveforms were corrected by way of reinstalling the latest firmware. 

Story starts here:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-bugs-missing-features-feature-requests/msg6230237/#msg6230237

Added to the OP POI list.

[mawyatt]

This seemed like a faulty scope but it wasn't.....



Instead the incorrect waveforms were corrected by way or reinstalling the latest firmware. 

Story starts here:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-bugs-missing-features-feature-requests/msg6230237/#msg6230237

Added to the OP POI list.

This is the kind of support outside the factory that anyone considering a DSO should consider. 

The support you, 2N3055, Performa01, tv84 and a few knowledgable others provide is simply outstanding

No other DSO OEM is even close to this level of after purchase support, even from the factory, and this support is outside the factory (and the factory isn't that bad to begin with)

Best

[AlekseyS]

Well, it only took me 6 years to finally get one of these 
Arrived this morning and made me very, very happy!
Haven't really had a chance to properly look into it, but from the first glance I love the display; the size, the brightness, snappy response...
Can't wait to start playing with this legendary scope

[AlekseyS]

Checked the AWG. At 10MHz it does look like a sine wave 

[AlekseyS]

Oh and huge thanks to this great person, who goes out of his way to help absolutely random people from around the globe. I personally thought I'd almost lost 2 pieces of equipment if it wasn't for Rob and his invaluable support.
Looking forward to another session at Warnbro Tav next time you're in Perth mate.
Cheers!!!

[tautech]

Well, it only took me 6 years to finally get one of these 
Arrived this morning and made me very, very happy!
Haven't really had a chance to properly look into it, but from the first glance I love the display; the size, the brightness, snappy response...
Can't wait to start playing with this legendary scope

Pleased you got one while the promotional 20% discount was still active Alex. 

Enjoy and looking forward to our next meetup in the Warnbro pub when we next visit our boi in WA.

[Martin72]

Can't wait to start playing with this legendary scope

We have 10 of them; they’ve been our “workhorses” for almost four years and have never let us down.

[KungFuJosh]

Can't wait to start playing with this legendary scope

We have 10 of them; they’ve been our “workhorses” for almost four years and have never let us down.

It has to be longer than that! I had mine for over 3 years, and I sold it in 2024...and I'm pretty sure you had them first. Or was that just your personal scope?

[KungFuJosh]

Checked the AWG. At 10MHz it does look like a sine wave 

Try 10bit mode when you don't need to go above 100MHz.

[Martin72]

It has to be longer than that! I had mine for over 3 years, and I sold it in 2024...and I'm pretty sure you had them first. Or was that just your personal scope?

That was my personal scope, purchased in 2019.
I tested it extensively before deciding to introduce the model to the company.
In 2022, we purchased the first units and again tested them for practicality in everyday use until we had equipped all test stations with them, because the scopes were so impressive.
The 2000X Plus was a milestone in professional scopes at an entry-level price.

[KungFuJosh]

Yeah, it's still a great scope. It was that darn metal handle that convinced me to upgrade at the time.

[AlekseyS]

Can't wait to start playing with this legendary scope

We have 10 of them; they’ve been our “workhorses” for almost four years and have never let us down.

I've been watching this scope for a while now, unfortunately it was a little on the high end of what I could spend without having to move into a dog box (wifes have a way of proving the point ). Plus I had a MSO5354, which is a great scope but a little too noisy on the front. So my journey to SDS2000X+ began by buying a SDS800X HD first. After about a year of using that, I so got used to the UI that the decision was made to get the 2000 after all. On top of that, like Rob has mentioned, Siglent were giving a 20% discount. It was a writing on the wall for me...

[AlekseyS]

Checked the AWG. At 10MHz it does look like a sine wave 

Try 10bit mode when you don't need to go above 100MHz.

I never need to go above 100 MHz as most of my tinkering is power supply type of work and som analog circuits (no RF).
So I will definitely try the 10 bit when I get home after work. Thanks for the tip.

[AlekseyS]

Can't wait to start playing with this legendary scope

We have 10 of them; they’ve been our “workhorses” for almost four years and have never let us down.

Even though, where I work we don't really need oscilloscopes, but I managed to push one through into the budget. It should be on site in a few days. This way I'll have one one at work too. 

[2N3055]

Yeah, it's still a great scope. It was that darn metal handle that convinced me to upgrade at the time.

Ahhh yess, the lustful handle that left no soul unstirred and no heart beating steady ..
The sheer poetry of scope handles ..
 

[KungFuJosh]

The sheer poetry of scope handles ..

🫰🫰🫰

[BillB]

A little something for Josh's pin-up wall...