Siglent SDS2000X Plus

[steve1515]

You can still offer an "Idiot's Guide" if you like but there's no longer any pressing need to do so on my part. Still, such a guide could prove itself useful in the future to deal with similar scenarios that will more than likely arise as time goes by.

What you did was correct. You should be able to paste it in a text file and run it. I believe in your case your default python is version 2 and the script wants version 3. You likely have it already installed and should just be able to run it at the command line with the python3 command. 

Code: [Select]

$ python3 siglent.py

[Johnny B Good]

You can still offer an "Idiot's Guide" if you like but there's no longer any pressing need to do so on my part. Still, such a guide could prove itself useful in the future to deal with similar scenarios that will more than likely arise as time goes by.

What you did was correct. You should be able to paste it in a text file and run it. I believe in your case your default python is version 2 and the script wants version 3. You likely have it already installed and should just be able to run it at the command line with the python3 command. 

Code: [Select]

$ python3 siglent.py

 You hit the nail right on the head! The installed version is, Python 2.7.6 (default, Nov 13 2018, 12:45:42). I did mention the version in one of these threads since I suspected this would likely cause the script to fail. Anyway, thanks to Elasia's work around, learning Python is no longer the high priority it once was.

John

[Electro Fan]

Siglent's SDS6000Pro also shares basically the same code with SDS2000X+ (and SDS5000X) adding the 2GHz and 4GHz options.

This is a very smart approach to product line / product family management as it spreads the initial development NRE across many more units and it allows bug fix and product improvement opportunities to be surfaced by a larger user base.  Plus for 2k+ users it is like buying real estate at the low end of a very nice neighborhood - it’s a great neighborhood for the the 5k and 6k neighbors but it’s an especially good deal for the 2k homeowners.

[Szybkijanek]

Question about Bode plot mode, I want to test my audio amplifier, is it good way?
" alt="" class="bbc_img" />

[tautech]

Question about Bode plot mode, I want to test my audio amplifier, is it good way?
(Attachment Link) " alt="" class="bbc_img" />

See Bode plot hookup images in this post:
https://www.eevblog.com/forum/testgear/rigol-mso5074-or-siglent-sds2104x-plus/msg3321894/#msg3321894

[Martin72]

Hi,

I would use a Voltage-Divider on the output of the Amp, depending on the state of it´s volume level.

[Szybkijanek]

Thanks for usefull informations, I try without 50Ohm impedance according to first method and maybe without divider because signal is small (ca 4VP-P).

[Bad_Driver]

Thanks ELASIA!

New script works perfect for the new options! I used the simple web page without login you suggested.
(And it worked from scope's UI)

One question: I'm wondering why the new script generates different keys for my "old", unlocked options than that before.
Example: AWG "old": 5M2Z3J36YFSKBP4K AWG with new script: 4TPWYG66II6I8KT5

Are there different keys working on the same device?

B.D.

[Szybkijanek]

What is procedure to choose load in options BP? Are 4: 50Ω, 75Ω, 600Ω and H-Z so when my DUT is audio amp. and load is 8Ω then must choose H-Z? And when DUT is e.g. RC filter then choose 50Ω? So what they are for 75Ω and 600Ω options load?

[tv84]

Are there different keys working on the same device?

No.

[Martin72]

What is procedure to choose load in options BP? Are 4: 50Ω, 75Ω, 600Ω and H-Z so when my DUT is audio amp. and load is 8Ω then must choose H-Z? And when DUT is e.g. RC filter then choose 50Ω? So what they are for 75Ω and 600Ω options load?

75ohm are for example video signals, 600 could stand for Audio (mic) and Hi-Z is above all, for example the input of your amp.

[Johnny B Good]

Are there different keys working on the same device?

No.

 I made a point of comparing the original list of license keys against the new list and they were identical (as expected).

John

[0xdeadbeef]

I still have the issue that I can't activate the Manchester key (being the last license) due to the issue described here (similar to the one described here)
Admittedly I have the SDS5000X but given that both scopes are supposed to run the same firmware, I'm puzzled that there is only one report similar to mine.
And even if I have asked that before: is the LCISL SCPI  command supposed to work for options on the SDS2000X Plus and SDS5000X or is this just a dummy implementation which always returns "OK" but doesn't actually do anything?

[Szybkijanek]

I activate Sent and Manchester without any problems and errors on SDS2000X+

[tv84]

How is your LCISL command written?

[0xdeadbeef]

I tried "LCISL MANC <key>" and several other things like "Manch" instead of "MANC". All resulted in an OK reply - even if I sent nonsense, but the Manchester option is still not activated.

[tv84]

Try: LCISL MANC,<key>

[0xdeadbeef]

Ah, you're right. That works. For some reason there are several pages/posts that state "LCISL <option> <key>" without the comma.
Anyway, thanks a lot!

[VanBudd]

Ive got the SDS2104X+ fully "upgraded" with the firmware 1.3.7R5 (should be the newest).

I have random issues after boot, mostly first boot the day.
No buttons or touchscreen react and no lights on the buttons. Screen is there but no signal.
Cant do anything, i waited 10 minutes still the same.
After reboot everything is normal and works as it should.
Dont know if its because of the "upgrade", didnt test the Osci much before entering the keys.

Does anyone have similar problems?

[tv84]

Reflash the FW.

[VanBudd]

Tried it yesterday, today the same problem.

The problem is that i cant reproduce the issue, its mostly the first boot of the day and after a reboot it works flawless for hours. 

[tubularnut]

Ive got the SDS2104X+ fully "upgraded" with the firmware 1.3.7R5 (should be the newest).

I have random issues after boot, mostly first boot the day.
No buttons or touchscreen react and no lights on the buttons. Screen is there but no signal.
Cant do anything, i waited 10 minutes still the same.
After reboot everything is normal and works as it should.
Dont know if its because of the "upgrade", didnt test the Osci much before entering the keys.

Does anyone have similar problems?

Just taken delivery of an SDS2104X+ direct from Siglent, 1.3.7R5, not upgraded yet, and boots ok. Will be attempting upgrades and let you know how it performs.

[tubularnut]

Upgraded and boots up in a a timely manner, same as out of the box, and fully functional.

[tautech]

Tried it yesterday, today the same problem.

The problem is that i cant reproduce the issue, its mostly the first boot of the day and after a reboot it works flawless for hours.

Things to try:
Secure erase to clear any hidden settings. (Save/Recall menu)
Factory Default then reboot then Self Cal.
Reboot.
Use normally.
Note settings at finish of day and if these have an effect on the next day instrument hang.

After above.
Just maybe we need connect you with a Siglent engineer so to get info from the scopes Debug menu so they can analyse what's going on.

[Elasia]

Tried it yesterday, today the same problem.

The problem is that i cant reproduce the issue, its mostly the first boot of the day and after a reboot it works flawless for hours.

Things to try:
Secure erase to clear any hidden settings. (Save/Recall menu)
Factory Default then reboot then Self Cal.
Reboot.
Use normally.
Note settings at finish of day and if these have an effect on the next day instrument hang.

After above.
Just maybe we need connect you with a Siglent engineer so to get info from the scopes Debug menu so they can analyse what's going on.

I dunno about that... it almost sounds like it needs to be heated before it starts to work which implies a broke connection, maybe a bad solder joint.. if its still in its return window i'd get another