Siglent SDS804X HD - Same 'Upgrade' Scripts?

[TomKatt]

Just ordered an SDS804X HD scope and researching what is needed to 'Upgrade' it for more memory.  If I understand correctly, the SDS800X series uses the same hacking script that worked for the SDS1104X-E scopes.  What is not clear to me after searching the forums is whether the options listed in the keygen code script are the same for the new SDS800X HD series and if the 50M -> 100M memory upgrade is it's own option or is simply related to the upper models...  So modifying the BW to 200MHz would result in the scope identifying as an SDS824X HD with 100M memory.  I did not observe any memory option code in the script.

Does the Python script require any modification for SDS800X specific options or does the script work exactly the same way?  I don't necessarily need the full 200MHz BW, but would like the ability to have more memory.  Of course if the two features are related it's not a bad thing to get both lol.

TIA

Edit - what are people entering for the model #?  "SDS800X-HD" ?

# Enter here the basic model
# You get this by running "MD5_PR?" at the SCIP prompt
# A sample: You have the SDS1104X-E than enter "SDS1000X-E"
# Some more basic models: "SDS1000X-E", "SDS2000X-E", "SDS2000X+", "SDS5000X", "ZODIAC-"
Model = 'SDS1000X-E'

[astromeier]

Hi TomKatt!

If I understand correctly, the SDS800X series uses the same hacking script that worked for the SDS1104X-E scopes.

Yes
I used this:
https://www.eevblog.com/forum/testgear/siglent-sds-sdg-hack-script

These lines I changed to:
Model = 'SDS800X-HD'
...
bwopt = ('70M', '100M', '200M')
...
otheropt = ('AWG', 'MSO', 'PWA')

I got my scope already improved to 200M, but compared the retrieved (command "MCBD?") key for the 200M option with the result of the script - bingo!

Coming from a 804 I would improve stepwise: 70M > 100M, Reset to factory default, 100M > 200M, Reset to factory default, self calibration, enjoy

My scope identifies as "SDS824X HD"

HTH Thomas

edit: otheropt

[TomKatt]

Got my SDS804X HD today...  The upgrade script worked perfectly!  Out of precaution I did upgrade it in steps 70 -> 100 -> 200 and then ran a calibration.  My scope now identifies as an SDS824X HD.   I have my own LA and AWG gear so have no need to enable those features in the scope.

Note to future owners - the serial number string is case sensitive.  I originally entered the serial number using all caps but noted that the calculated code for 70Mhz did not match the code returned by the MCBD? query - knowing it needed to be the same code I then pasted my serial number as displayed on the SCPI Home screen and ran the script again.  When the script code for 70MHz matched my scope's code I then proceeded to upgrade.

Thanks again!

[tautech]

Got my SDS804X HD today...    I have my own LA and AWG gear so have no need to enable those features in the scope.

Which needs its firmware updating to work correctly with SDS800X HD models:
https://int.siglent.com/download/firmwares/?ProId=74

[TomKatt]

I should have clarified - I have my own dedicated LA and AWG gear - not Siglent scope modules.

But thanks for the information.

[awakephd]

Well, that turned out to be easy. Just followed the script to get the scope id, serial number, and model number and edit those into the script. I did as others suggested and upgraded from 70M - 100M, default to factory, then 100M to 200M, default to factory. It now identifies as an 824 rather than an 804. Currently it is running the self-calibration.

One thing that I noticed - in the Acquire menu, I could still only choose 50M as the maximum memory depth (single channel), but when I adjust the horizontal timebase, I see that it is going up to 100M points.

On edit: after rebooting and doing a self-calibration, it is now showing 100M as the maximum option under Acquire - Menu - Max Memory Depth. Interestingly, it no longer shows 50M as an option in this list (when single channel is enabled - of course it drops to 50M when two channels are enabled).

Very cool that this is so straightforward to do. Thanks to those who put together the script and gave instructions!

[TomKatt]

I have no way to test this, but I find it very interesting that upgrading to 200Mhz apparently also increases waveform capture rate by 50% (80K -> 120K wfm/s) in addition to doubling the memory from 50M -> 100M...  Is there some correlation between memory and capture rate or do the <200MHz models have some software performance constraint?

[tautech]

I have no way to test this, but I find it very interesting that upgrading to 200Mhz apparently also increases waveform capture rate by 50% (80K -> 120K wfm/s) in addition to doubling the memory from 50M -> 100M...  Is there some correlation between memory and capture rate or do the <200MHz models have some software performance constraint?

See P2 of the datasheet:
https://int.siglent.com/u_file/download/24_03_27/SDS800X%20HD_Datasheet_EN01C.pdf

[TomKatt]

See P2 of the datasheet:
https://int.siglent.com/u_file/download/24_03_27/SDS800X%20HD_Datasheet_EN01C.pdf

Yes - that's where I obtained the specs.  But I'm still amazed (confused) that in addition to bandwidth, the performance is also increased simply by software.  My question is if the additional memory allows the capture rate to increase as well?

Edit - I guess that bandwidth itself could be considered a performance measurement, and other products have been similarly constrained to differentiate model capabilities...

[KungFuJosh]

constrained to differentiate model capabilities...

That's how it generally works. Cheaper to make all the hardware the same, and charge extra for licensing and/or front panel stickers.

[electr_peter]

Note letter case carefully in settings:

Code: [Select]

SCOPEID = '0123450abcd12345'
SN = 'SDS00ABCD01234'
Model = 'SDS800X-HD'
These options codes do not work:

Code: [Select]

otheropt_not_working = ('FG', '16LA', 'PA')Use these codes instead:

Code: [Select]

otheropt = ('AWG', 'MSO', 'PWA')

[astromeier]

Thanks for testing
Edited my post ...

[tttonyyy]

I've got an SDS 1202X-E which is their genuine 200MHz scope and just bought a SDS804X HD.

Successfully re-licensed the latter to 200MHz, though I went directly to the 200MHz key without any factory resets between, in fact if you stick a 200MHz signal in you can see the amplitude change live between pasting the SCIP MCBD keys, I switched between 70, 100 and 200 and back-and-forth on the fly without any issues.

Comparing the SDS1202X-E measurements with the re-licensed SDS804X HD using the same PP215 probe, all looks good. 

Mine came with 1.1.36 firmware and I updated to 1.1.38 for the latest UI changes.

Even with the supplied PB470 70MHz probes it's possible to spot a 400MHz carrier using the FFT, I'm pretty happy with it.





As above but with with interpolation off:

[davidabc]

Has anyone been successful in using the TP-Link TL-WN725N USB Wifi Dongle with the SDS800X to connect the scope to the local network? 

Keeping to this topic thread, is a key or unlocking script required to be able to use the TL-WN725N?  If so, how?

I prefer Wifi to ethernet and the USB Wifi dongle is much smaller and easier to use than an ethernet to Wifi adapter.

Thanks in advance.

[ttelectronic]

Has anyone been successful in using the TP-Link TL-WN725N USB Wifi Dongle with the SDS800X to connect the scope to the local network? 

Keeping to this topic thread, is a key or unlocking script required to be able to use the TL-WN725N?  If so, how?

I prefer Wifi to ethernet and the USB Wifi dongle is much smaller and easier to use than an ethernet to Wifi adapter.

Thanks in advance.

I ordered one to test, will know tomorrow afternoon.   

[tautech]

Has anyone been successful in using the TP-Link TL-WN725N USB Wifi Dongle with the SDS800X to connect the scope to the local network? 

Not AFAIK.

Keeping to this topic thread, is a key or unlocking script required to be able to use the TL-WN725N?  If so, how?

WiFi connectivity with TL-WN725N was an Option for SDS12/1104X-E and SDS23502/2202X-E and these models had the OS SW preinstalled to support TL-WN725N.
The WiFi option for SDS12/1104X-E models was removed/permanently enabled in recent firmware.

Sadly none of this is currently the case for SDS800X HD models as they use the quite different UI and OS of their bigger brothers, none of which support WiFi connectivity.

Yes, we've asked and pleaded for TL-WN725N and WiFi connectivity to be supported but it's low priority if it ever happens. 

I prefer Wifi to ethernet and the USB Wifi dongle is much smaller and easier to use than an ethernet to Wifi adapter.

100%, me too but for the meanwhile we use TP-Link TL-WR802N or similar.....which does have the advantage that it can be used on any instrument with LAN capability....or connected to a LAN switch to allow more instruments/devices to use WiFi.

[davidabc]

100%, me too but for the meanwhile we use TP-Link TL-WR802N or similar.....

Thanks for your reply.
I was wondering whether the limited speed of the 10/100 Mbps Ethernet on the TL-WR802N (effectively only about 10MBps) affects the interface performance and response when connected to the scope?  In other words, would it be better to find a Ethernet to Wifi adapter which has a Gigabit Ethernet connection?

[ebastler]

I was wondering whether the limited speed of the 10/100 Mbps Ethernet on the TL-WR802N (effectively only about 10MBps) affects the interface performance and response when connected to the scope?  In other words, would it be better to find a Ethernet to Wifi adapter which has a Gigabit Ethernet connection?

While the frame rate which the SDS800X HD can provide via its web interface is not great, I am pretty sure the bottleneck is not the Ethernet connection but the software stack. And the LAN port on the scope itself is only 10/100 Mbit/s anyway.

[davidabc]

I ordered one to test, will know tomorrow afternoon.   

Good luck.  That's timely that you testing it so soon.  Let us know how it goes.

[ebastler]

Has anyone been successful in using the TP-Link TL-WN725N USB Wifi Dongle with the SDS800X to connect the scope to the local network? 

I ordered one to test, will know tomorrow afternoon.   

I have one of those WiFi dongles, from my brief stint with the Rigol DHO1074. Can't see how it would work with the SDS800X HD -- it lacks the device driver (to my knowledge), and it certainly lacks a UI to enter the WiFi network name and password.

[ttelectronic]

What a bear it is to get it off the usb port by hand. Indeed, there is no support fir the 725 or the 821 tp link.

Hoping they will add support it one day. My Keysight scope doesn't support wifi or lan. So I'm relatively happy that it at least supports LAN, wifi would be a little more convenient.

I agree with ebastler, the bottleneck is not the network for VNC. I played around with it a bit and even at low quality settings on the VNC client the update rate is the same.

[KungFuJosh]

wifi would be a little more convenient

A mini wifi bridge will get you wifi on the scope without taxing the scope's resources with wifi drivers.