Siglent SDS804X HD - Same 'Upgrade' Scripts?

[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)?

[fugazi]

Hi All,

The obvious, does this "modification" still applies for current firmware versions? I am planning to buy a 804x hd.

Br

Fugazi

[simcc]

Hi, has anyone noticed their SDS804X HD start "hanging" since upgrading to SDS824? Otherwise it seems to be working fine, but often enough it just hangs and I have to powercycle it...usually if I'm doing some stacked math stuff (like F1 = C1-C2, F2 is FFT of F1, that kind of thing)...

I followed instructions, 70-100, load factory, then 100-200, load factory, then calibrate...maybe I should have power cycled before each bump up?

I tried default and load factory settings etc. a few times...I haven't tried a Hardware Reset, do i need to backup all my saved settings for that, or is there any point trying it anyway.

I wonder should I try just downgrade it back to 70...I don't 100% need 200 MHz really, (there was just one thing I wanted to look at).

[hfleming]

Hi, has anyone noticed their SDS804X HD start "hanging" since upgrading to SDS824? Otherwise it seems to be working fine, but often enough it just hangs and I have to powercycle it...usually if I'm doing some stacked math stuff (like F1 = C1-C2, F2 is FFT of F1, that kind of thing)...

I followed instructions, 70-100, load factory, then 100-200, load factory, then calibrate...maybe I should have power cycled before each bump up?

I tried default and load factory settings etc. a few times...I haven't tried a Hardware Reset, do i need to backup all my saved settings for that, or is there any point trying it anyway.

I wonder should I try just downgrade it back to 70...I don't 100% need 200 MHz really, (there was just one thing I wanted to look at).

Nope. Mine works just fine after the upgrade. Have you tried resetting your unit back to factory defaults after upgrading?

[kbk]

I just joined the group today.
Yesterday I ordered a Siglent SDS804X HD at Amazon, it should arrive in a weeks time.
I read all the posts regarding the upgrade and also watched the YouTube video
"TTE #28 - Siglent SDS804X HD - Upgrade To An SDS824XHD" several times.
Also downloaded and installed on the desktop siglentkeygen.zip and siglent.py respectively.
Either I missed in the video or it is not mentioned how and at what time in the upgrade process the scope would have to be connected to the computer (Windows 10 Pro, x-64 based PC). I can only speculate that a USB connection from the scope to the PC could be used.
Since I don't want to wait with the upgrade until the warranty expires, I wonder if the scope would be rendered useless if the the upgrade failed. - Can the original condition (i.e. 804) be restored?
Thanks in advance for any comments.

[tautech]

I just joined the group today.
Yesterday I ordered a Siglent SDS804X HD at Amazon, it should arrive in a weeks time.
I read all the posts regarding the upgrade and also watched the YouTube video
"TTE #28 - Siglent SDS804X HD - Upgrade To An SDS824XHD" several times.
Also downloaded and installed on the desktop siglentkeygen.zip and siglent.py respectively.
Either I missed in the video or it is not mentioned how and at what time in the upgrade process the scope would have to be connected to the computer (Windows 10 Pro, x-64 based PC). I can only speculate that a USB connection from the scope to the PC could be used.

Welcome to the forum.

LAN connectivity should instead be used to access the scopes internal webserver that provides the scopeid for use in the script.

Since I don't want to wait with the upgrade until the warranty expires, I wonder if the scope would be rendered useless if the the upgrade failed. - Can the original condition (i.e. 804) be restored?

Then with the webserver SCPI command page you can issue commands to get the OEM BW license should it be needed to return the scope to original configuration.

The advantage of using the webserver SCPI command page is any SCPI commands are accepted or rejected unlike a telnet into the scopes code where you certainly can brick an instrument.

[kbk]

Thank you for the useful information.
I guess I can use a USB-WiFi adapter or a RJ45 Ethernet cable from the scope to connect to my Router.
The scope I ordered is already on the way to me. - I want to report on my findings, success or failure.

[MalcolmX]

11/17/2025; 6:18PM; Script still works

[Zucca]

Got the 804x scope today.

1) upgraded FW from 1.1.3.8 to  1.1.6.5
2) upgraded to 200MHz in steps with fact. reset in between
3) installed the PWA license

Tested the bandwidth before and after the 200MHz, with the Leo Bodnar Pulse generator terminated to 50Ohm externally.
Before:

After:


I then ran a self cal, this is the final result:


using the formula

BW is about .35/tr

I get about 243-241 MHz of bandwith.

Yes, all the 4 channels similar numbers.

Happy!

PS: @Siglent: I would never have bought this scope without knowing there was a keygen available...