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.

[davidabc]

Currently it is running the self-calibration.

Just wondering how long the self-calibration took for you?  Some say about 30 minutes, but I heard 5 minutes too.

[tautech]

Currently it is running the self-calibration.

Just wondering how long the self-calibration took for you?  Some say about 30 minutes, but I heard 5 minutes too.

Expect ~5 minutes

[davidabc]

Thanks tautech

[davidabc]

I ordered one to test, will know tomorrow afternoon.   

It didn't work?!

[davidabc]

I ordered one to test, will know tomorrow afternoon.   

It didn't work?!

[ttelectronic]

I ordered one to test, will know tomorrow afternoon.   

It didn't work?!

Nope it did not, I did try. Drivers are not on the scope.

[davidabc]

I ordered one to test, will know tomorrow afternoon.   

It didn't work?!

Nope it did not, I did try. Drivers are not on the scope.

Thanks for trying.

[awakephd]

Sorry that I missed your question, but Rob has answered it. It has been long enough that I don't really recall, but 5 min. sounds about right.

[ericwil76]

I am at a loss I got the script and all the SCIP information SN so on. I opened PuTTY and connected but I can't type, the cursor is not blinking. I am using port 5024 and my IP what am I missing?

[tautech]

I am at a loss I got the script and all the SCIP information SN so on. I opened PuTTY and connected but I can't type, the cursor is not blinking. I am using port 5024 and my IP what am I missing?

If you're trying to access the scopes OS, < STOP, that's not needed.
Do some more homework.

[ericwil76]

What kind of help is that do some more homework. I can't find any more info and only trying to follow the instructions.

[tautech]

What kind of help is that do some more homework. I can't find any more info and only trying to follow the instructions.

Can you access the webserver SCPI command page ?
Follow the link in reply #1 in this thread.

With the right command and license you install licenses with just Copy/Paste and if wrong nothing happens.
While any SCPI command returns Success when sending, correct or not, you can't do any damage to the OS and brick your scope.

Poking around with Telnet is not advised and not needed.

[ericwil76]

Man, these instructions are not clearly written. It appeared I needed to SSH into the scope which failed for me for some reason. Why those instructions even exist I have no idea. I did just now successfully run the key generator Python script in an online debugger and was able to get a return of my upgrade codes.

So now I have to enter the code "MCBD ##########" into the WebServer SCPI command line?

How am I supposed to check my codes if I can not access the scope over telnet?

[tautech]

How am I supposed to check my codes if I can not access the scope over telnet?

With a SCPI command.

[ericwil76]

I entered my 100M key in the SCPI command line and nothing says command sent successfully but scope still only recognized as 70M

My scope id and sn are spot on exact.

Still stumped

[ericwil76]

Ok I got it to work I was off by a " - " in the model number and was finally able to get the codes to match and successfully upgrade to 100M

How do I do a factory default reset. Nothing in manual been all over menus can't find a factory reset?

[ebastler]

How do I do a factory default reset. Nothing in manual been all over menus can't find a factory reset?

I was about to suggest "RTFM", but indeed I can't find that info either. Section 29.1 of the manual states that the "Default" button on the front panel has two modes, either "reset to last saved default" or "reset to factory default". But where the heck do I choose between these modes? Can't find anything in the manual or in the scope's Utility menu.

[Kaylan]

How do I do a factory default reset. Nothing in manual been all over menus can't find a factory reset?

According to siglent:

Oscilloscope Hardware Reset

1. Disconnect all USB, LAN, and input cables. ...
2. Power cycle the instrument by pressing the power button.
3. Immediately begin pressing the MATH button repeatedly at a rate of 2 to 3 times a second while the instrument boots up.
4. If the instrument does not boot up properly, retry steps 2 through 4.

HOWEVER, i don't see a need to do this, and i'm not even sure this is the kind of reset we're looking for. This may completely reset the license keys to factory default also. When i upgraded my SDS-812X HD to an SDS-822X HD (100MHz -> 200MHz) last night, i rebooted normally, used the default button, then ran a self calibration as the scope had been running for over 30 minutes. I have had no issues. My scope identifies as SDS822X HD, has the upgraded memory (and wave form capture rate i suppose?). Those reset instructions are for "In some extreme hardware errors, the oscilloscope may become unresponsive or “hang” during the boot sequence."
https://siglentna.com/operating-tip/oscilloscope-hardware-reset/

[2N3055]

load/save menu.
load factory default

[sims070]

Hey,

So what can be upgraded on the siglent sds804x hd? Only the bandwidth to 200 MHz and the memory depth to 100 Mpts?
Regards

[PickyAudioGuy]

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.

How do you find the "SCPI Home screen?"

I may have answered this myself...  I just changed my serial number (queried from *IDN?) to all lower case and my MCBD query matches my scope as it is currently at 70MHz.

Are we to assume that putting the original code in will put the scope back to original?

Does anyone know if the latest firmware breaks this script?

[tv84]

Are we to assume that putting the original code in will put the scope back to original?

Does anyone know if the latest firmware breaks this script?

We are.

Does not.

[F4]

Someone has done a video tutorial of the process:

[STEVEWEST]

Just got an SDS800X-HD and the script work perfect.

[rs38]

does it also work with the new firmware? und does the hack "survive" a firmware update?

[igoris]

does it also work with the new firmware? und does the hack "survive" a firmware update?

It does. I got a brand new SDS804, updated it to 1.1.6.2, then used the script to get it to 200MHz and unlock PA

[igoris]

Interestingly, though, I don't have an option to activate AWG and MSO. Not sure if they become available only after the corresponding devices are connected to the scope

[tautech]

Interestingly, though, I don't have an option to activate AWG and MSO. Not sure if they become available only after the corresponding devices are connected to the scope

The need for MSO & AWG licences were removed in V1.1.3.8 firmware last year.

MSO & AWG modules can now be connected to any SDS800X HD without the need for licensing.

[crysti]

After activating my SDS814X with MCBD, it lost linearity — now it's limited to 10 MHz. Do you have any idea how I can revert it or at least restore the linearity up to 100 MHz, as it originally was? I checked the signal level with another oscilloscope, which shows the same level up to 100 MHz.

[2N3055]

After activating my SDS814X with MCBD, it lost linearity — now it's limited to 10 MHz. Do you have any idea how I can revert it or at least restore the linearity up to 100 MHz, as it originally was? I checked the signal level with another oscilloscope, which shows the same level up to 100 MHz.

Do you by any chance have 20MHz BW limiter ON on a channel?

[crysti]

After activating my SDS814X with MCBD, it lost linearity — now it's limited to 10 MHz. Do you have any idea how I can revert it or at least restore the linearity up to 100 MHz, as it originally was? I checked the signal level with another oscilloscope, which shows the same level up to 100 MHz.

Do you by any chance have 20MHz BW limiter ON on a channel?

The first time I tried this, if I activate the 20 MHz BW, the signal level drops even more.
I tried resetting the power button with the Math button, calibrating, updating and downgrading the firmware.

[TomKatt]

After activating my SDS814X with MCBD, it lost linearity — now it's limited to 10 MHz. Do you have any idea how I can revert it or at least restore the linearity up to 100 MHz, as it originally was? I checked the signal level with another oscilloscope, which shows the same level up to 100 MHz.

I respectfully suggest some kind of user error in your setup...  What does the scope info screen show for model number etc?  Unless you somehow managed to set the scope to some strange model number, the BW should not be affected and I have not heard this complaint before.

Also, where did that graph come from? 

[tautech]

After activating my SDS814X with MCBD, it lost linearity — now it's limited to 10 MHz. Do you have any idea how I can revert it or at least restore the linearity up to 100 MHz, as it originally was? I checked the signal level with another oscilloscope, which shows the same level up to 100 MHz.

Measured how ?
Signal source ?

Likely you installed an incorrect upgrade license.
Did you first check the script returned the correct license for your SDS814X HD before applying an upgrade ?

[crysti]

After activating my SDS814X with MCBD, it lost linearity — now it's limited to 10 MHz. Do you have any idea how I can revert it or at least restore the linearity up to 100 MHz, as it originally was? I checked the signal level with another oscilloscope, which shows the same level up to 100 MHz.

Measured how ?
Signal source ?

Likely you installed an incorrect upgrade license.
Did you first check the script returned the correct license for your SDS814X HD before applying an upgrade ?

I measured an RF signal generated by the TinySA Ultra using a second 100 MHz oscilloscope. I tested both with an oscilloscope probe and with an RF cable and 50 Ohm terminator — the result was the same. I verified that the generated code matches mine for 100 MHz, and I upgraded it to 200 MHz using MCBD.

[2N3055]

I tried resetting the power button with the Math button, calibrating, updating and downgrading the firmware.

 None of that stuff has influence.

I would venture a guess you used some license string that is wrong so scope "upgraded" to some random config.

Reapply 70MHz license. Verify that scope works fine.
Then 100 MHz and verify again.
Then try 200 again.

[tautech]

After activating my SDS814X with MCBD, it lost linearity — now it's limited to 10 MHz. Do you have any idea how I can revert it or at least restore the linearity up to 100 MHz, as it originally was? I checked the signal level with another oscilloscope, which shows the same level up to 100 MHz.

Measured how ?
Signal source ?

Likely you installed an incorrect upgrade license.
Did you first check the script returned the correct license for your SDS814X HD before applying an upgrade ?

I measured an RF signal generated by the TinySA using a second 100 MHz oscilloscope. I tested both with an oscilloscope probe and with an RF cable and 50 Ohm terminator — the result was the same. I verified that the generated code matches mine for 100 MHz, and I upgraded it to 200 MHz using MCBD.

Sounds like you did things correctly.

Now try Default just in case too little sampling/memory depth is set which acts like a BW filter.

[crysti]

I returned to 100MHz and it is now normal. Has anyone checked the input signal level after activation to see if it is displayed correctly? I have Uboot 3.8.12, FPGA 2024-04-11, Hardware ver 00 and firmware 1.1.3.8

[2N3055]

I returned to 100MHz and it is now normal. Has anyone checked the input signal level after activation to see if it is displayed correctly? I have Uboot 3.8.12, FPGA 2024-04-11, Hardware ver 00

Again, like other people told you..
There should be no problem.
824xHD has in excess of 250MHz BW.

You are doing something wrong or your scope is first having problems with this,  out of thousands that had no problem with this.
Make sure you are generating proper code.
I cannot help you more than this. I don't know details how it's done, i never did it on my scopes. But I know other people had no problems.

[tautech]

I returned to 100MHz and it is now normal. Has anyone checked the input signal level after activation to see if it is displayed correctly? I have Uboot 3.8.12, FPGA 2024-04-11, Hardware ver 00 and firmware 1.1.3.8

Quick and dirty test with SDG6022X of what was a SDS814X HD yesterday......
Cursors set to 100 MHz levels....

[crysti]

I partially solved it by activating 200MHz with an older firmware, there is a protection somewhere

[tautech]

I partially solved it by activating with an older firmware, there is a protection somewhere

My quick and dirty test was with a beta FW......

I should do another properly accurate test with a RF gen.......that result should provide a -3dB point well over 200 MHz.
However other tasks are calling.......

[tautech]

I partially solved it by activating with an older firmware, there is a protection somewhere

BTW, did you run a Self Cal at any stage ?

[crysti]

I partially solved it by activating with an older firmware, there is a protection somewhere

BTW, did you run a Self Cal at any stage ?

Certainly

[crysti]

Finally, I managed to reach 200 MHz. This is how a 125 MHz square wave signal with Trise = 1 ns looks when measured with a 350 MHz probe.

[tyeth]

Finally, I managed to reach 200 MHz. This is how a 125 MHz square wave signal with Trise = 1 ns looks when measured with a 350 MHz probe.

I'm curious what was the final missing thing, did you just go back through the upgrade process from the start (adjusting the serial number or something)?