Siglent SDS2000X Plus

[Peter_O]

My SDS2104X plus, bought January 2021 does not start any more.

When pressing the power button at the front, the button lights up, but no fan, no screen, no further button lights.
Same after disconnecting all connection or trying different power cord, which are double checked and known good anyway.
Pressing lit button for some seconds makes it to unlight again.

I found the hint and pressed "Math" repeatedly during power on, but with no effect.
https://siglentna.com/operating-tip/oscilloscope-hardware-reset/

Yesterday it run as usual, normal power off and shut down.

Any ideas?

Finally I have the Scope back fully functional.

After contact with the dealer I got a free shipment voucher and sent it to Siglent EU in germany directly.
Arrived at Siglent's Mai 3rd.

Got the same device back Mai 20th with mainboard changed.
Old was HW version 02-04, FPGA 2020-09-23
New is 02-00, 2021-07-16
It came without the initially bought option package installed.
Contacted dealer.

Got official Siglent authorization codes June 4th. These can be traded into installation codes on Siglent's website.
Didn't work, most probably they were generated for the old mainboard.
Contacted dealer.
Reminded dealer.

Got installation codes directly from dealer July 7th which worked fine.

If you need the options for business you should think of a fallback solution, e.g. a 2nd device.

For me it's OK, the initial turn around time of 2 weeks is fine.
And it's fine that Siglent has a local EU service point in DE.

From overall perspective the rough options processes might be quite OK for hobbist's market and prices too.

[Bad_Driver]

My SDS hangs during boot now too! All the lights are flashing, the relais are clicking as usual but it stops with the „Siglent“ logo on black background. Some times I can overcome this with the repeatedly pressing of „Math“ key during the boot process (as Peter_O noticed), sometimes not. It also hangs during self calibration process. I had the same issue with my SSA3000+ some weeks ago but with „system reset“ and the last firmware upgrade the problem is gone.

Bought in June 20 I hope that Siglent remembers their 3 year warranty promise. Are there others out there with the same problem?

btw: Is someone knowing how to remove the „liberation“ licences from the device? I remember that there must be a SCPI command….

Strange: My "old" scope has HW-version 2.00 and FPGA 2021-07-16 (after update) as Peter_O's after repair!

[Martin72]

I´ve got the strange feeling it could have to do with the latest firmware updates...
Me I never got any problems with my one of the very first scopes - The buyer told me a few days after receiving, that the scope hangs while booting (one time, after the reset-thing it worked).
Last things I´ve done with it was the updating..

[Bad_Driver]

No, the new firmware is not the reason.

During fiddling with booting the device (with the "math" key trick) I mentioned that it was still on 1.3.5R5.
When I got it again up and running I just updated it to the last 1.3.9R12 - but it didn't boot again without the trick.

As we all suffer in Germany from the highest energy costs worldwide and the Siglents standby consumption is
to high all my devices are always hard switched off and the Siglent SDS and my SSA
are set to "Power on line enable".

Since I had the same problem with my SSA I start thinking that this could be the reason?

[BmaxTom]

btw: Is someone knowing how to remove the „liberation“ licences from the device? I remember that there must be a SCPI command….

LIC:DEL optioncode

[2N3055]

No, the new firmware is not the reason.

During fiddling with booting the device (with the "math" key trick) I mentioned that it was still on 1.3.5R5.
When I got it again up and running I just updated it to the last 1.3.9R12 - but it didn't boot again without the trick.

As we all suffer in Germany from the highest energy costs worldwide and the Siglents standby consumption is
to high all my devices are always hard switched off and the Siglent SDS and my SSA
are set to "Power on line enable".

Since I had the same problem with my SSA I start thinking that this could be the reason?

Hard switched off? Do you shutdown devices first? You have to do that, shutdown to "soft off". Then only you can switch off the power...

[Bad_Driver]

I alway shut down the devices with the power button (soft off), after that I disconnect it from mains. No hard switch off of course!

[2N3055]

I alway shut down the devices with the power button (soft off), after that I disconnect it from mains. No hard switch off of course!

No offense meant, I just wanted to make sure... 
It should not make difference in that case. But some of the devices might have issue if you change something and immediately (within seconds) quickly shutdown device, before all is saved..

[Bad_Driver]

It‘s clear that this modern devices are more computers than simple measurement tools 
No regrets needed!

[Bad_Driver]

LIC:DEL optioncode

Worked for all the licences but not for the bandwidth. Any hint how to remove the bandwidth extension? Thanks in advance!!

[tv84]

LIC:DEL optioncode

Worked for all the licences but not for the bandwidth. Any hint how to remove the bandwidth extension? Thanks in advance!!

You don't remove it. You just license the original BW.

[Bad_Driver]

MCBD <lic> (lic= Licence for 100M) worked!

Now I'm back with a virgin SDS2104X Plus. But after several shutdowns and reboots the system does not hang anymore.....
 

[Martin72]

Now I'm back with a virgin SDS2104X Plus.

That´s what you hope..

But after several shutdowns and reboots the system does not hang anymore.....

Maybe contact the siglent support anyway, perhaps it´s a known thing for them and they got a explanation.

[Bad_Driver]

Martin you are right! 

After re-licensing everything the system today hangs again! I got a very fast reply from the Siglent service with a recovery file and I performed the
described procedure incl. update to the latest firmware (the recovery image is from 2020) but it still hangs.

Now I have to go for the RMA process 

 

[Martin72]

I got a very fast reply from the Siglent service with a recovery file and I performed the
described procedure incl. update to the latest firmware (the recovery image is from 2020) but it still hangs.

And when you do not update to the latest firmware ?
If possible, recover again and leave it as it is, test a while, then update to the latest fw for the "old" hardware (R9) and see what happen.
If it don´t freeze anymore, "re-license" it...

[Bad_Driver]

As mentioned above the hanging starts with firmware 1.3.5R5, I missed the updates. May be I have to many Siglent devices to stay with all up-to-date 
But it hangs with latest firmware too.

[thinkfat]

What is then the last "safe" version to upgrade to?

[Bad_Driver]

I think it is not a question of firmware.

I was on 1.3.9R6 (Oct 21) when "boot hanging" started this weekend. I will now send back the device for repair.

(my relpy to Martin72 were I stated "1.3.5R5" is wrong)

[Martin72]

Please report what will be done by siglent when it returns.

[Bad_Driver]

Now the SDS is ready for DHL but in this minute I found in the SSA thread the hint that the SDS can hang when
you use an unusual attenuation factor in the channel menu.

https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg4298731/#msg4298731

I worked when the hanging starts with my LNA for some noise measurements and set the channel attenuation to 0.01 (40 dB) and 0.001 (60 dB).

Can someone check this? You always overcome hanging with repeatedly pressing „math“ during boot (3 times a second). But you must do a real shutdown and not a reboot to check it.

[Performa01]

Now the SDS is ready for DHL but in this minute I found in the SSA thread the hint that the SDS can hang when
you use an unusual attenuation factor in the channel menu.

https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg4298731/#msg4298731

I worked when the hanging starts with my LNA for some noise measurements and set the channel attenuation to 0.01 (40 dB) and 0.001 (60 dB).

Can someone check this? You always overcome hanging with repeatedly pressing „math“ during boot (3 times a second). But you must do a real shutdown and not a reboot to check it.

Just tried it with my very early pre-production SDS2354X plus, HW-Rev. 02-00, FW-Version 1.5.2, Uboot-Version 5.0.

I set both custom probes, one to 0.01, the other one to 0.001, then activated both of them one after the other and did a shutdown via the Utility menu. In both cases the scope booted up without any problems afterwards.

[Bad_Driver]

Now I unpacked my SDS from the prepared DHL parcel and checked it by myself again.

If I set attenuation CH1 to 1:1 system reboots after shutdown and disconnected from mains.
Reconnect to mains ("Power on line enable" active)
System boots.

Attenuation set to 1:100 (0.01), same procedure, system hangs.

SDS is production date April 2020. Latest firmware. HW 2.00

[tautech]

Now I unpacked my SDS from the prepared DHL parcel and checked it by myself again.

If I set attenuation CH1 to 1:1 system reboots after shutdown and disconnected from mains.
Reconnect to mains ("Power on line enable" active)
System boots.

Attenuation set to 1:100 (0.01), same procedure, system hangs.

SDS is production date April 2020. Latest firmware. HW 2.00

This is the hard bit with any obscure bug, finding a 100% repeatable setup for the chaps at Siglent be be guaranteed to reproduce it.   

[Deichgraf]

Now the SDS is ready for DHL but in this minute I found in the SSA thread the hint that the SDS can hang when
you use an unusual attenuation factor in the channel menu.

https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg4298731/#msg4298731

I worked when the hanging starts with my LNA for some noise measurements and set the channel attenuation to 0.01 (40 dB) and 0.001 (60 dB).

Can someone check this? You always overcome hanging with repeatedly pressing „math“ during boot (3 times a second). But you must do a real shutdown and not a reboot to check it.

My SDS has the same feature 

I checked only one channel (CH1) and beside 0.01 also 0.999 with the same result.
So attenuation values below 1 will (most probably) produce a system hang after a cold start (mains disconnected) .

The system BIT after startup has maybe a problem with such "unusual" values!?

For details see pictures.

[Martin72]

Puuhh..

This is hard - but otherwise, who in the heck will come in a situation to determine such a ratio ?