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