Siglent SDS2000X Plus

[Elasia]

This is part why I did try to get to the front of the pcb as well, only the back side can be confirmed to have identical hardware components, and yeah i ignored the silkscreen

Mine taps out at around 550Mhz for its front end

[edigi]

SN# !
His newly purchased SDS5034X was older than my SDS5054X bought mid 2019.

What are the good SN#s?
What if the same digital filter (probably FIR in FPGA) that is used to restrict the BW in lower models is used to boost the upper side of the spectrum in the top model (and the increased noise is treated with BW limit in low mV/div settings)?

[Elasia]

SN# !
His newly purchased SDS5034X was older than my SDS5054X bought mid 2019.

What are the good SN#s?
What if the same digital filter (probably FIR in FPGA) that is used to restrict the BW in lower models is used to boost the upper side of the spectrum in the top model (and the increased noise is treated with BW limit in low mV/div settings)?

The unit uses a hardware chip in the front end that is able to change the limit, Dave shows it and a datasheet in his video

[edigi]

The unit uses a hardware chip in the front end that is able to change the limit, Dave shows it and a datasheet in his video

I guess that's for 20 and 200MHz. What's the chip btw?

[0xdeadbeef]

The unit uses a hardware chip in the front end that is able to change the limit, Dave shows it and a datasheet in his video

I guess that's for 20 and 200MHz. What's the chip btw?

The LMH6518 is a digitally controlled variable gain amplifier with built in bandwidth limitation. It can limit to 20, 100, 200, 350, 650 and 750MHz. So it's justified to believe that it's also used to limit the scope's bandwidth to 100, 200 and 350MHz.

[Martin72]

6) Open a command window on PC, write 'telnet +IP address of your scope'

Can someone try this with the new firmware installed ?
Tried this a few minutes ago and it fails - "Connection refused"....
Maybe the new fw is the reason.
Will downgrade and test it again - Later….

[edigi]

The unit uses a hardware chip in the front end that is able to change the limit, Dave shows it and a datasheet in his video

I guess that's for 20 and 200MHz. What's the chip btw?

The LMH6518 is a digitally controlled variable gain amplifier with built in bandwidth limitation. It can limit to 20, 100, 200, 350, 650 and 750MHz. So it's justified to believe that it's also used to limit the scope's bandwidth to 100, 200 and 350MHz.

Why is it then that if the BW restriction is active and significantly higher frequency sine than the limit is connected (let's say 2x the BW) the display cannot be filled vertically with the signal?
If a lower V/div is attempted, there will be all kind of artifacts like increased sensitivity resulting in smaller signal displayed and shifted vertically (and the signal falls apart very quickly if continued). I've interpreted it as a sign that the analogue side (including ADC) is overdriven but it's not directly obvious from the display since the digital filter attenuates the signal only after the analogue part.
So I've assumed that a pure filtering loss in the analogue side can be compensated with increased gain.
But maybe I've guessed it wrong.

Another issue is that based on datasheet the afformentioned chip's -3dB point is at 900MHz. A bit low for 1GHz and a bit on the high side for 500MHz.

[thinkfat]

6) Open a command window on PC, write 'telnet +IP address of your scope'

Can someone try this with the new firmware installed ?
Tried this a few minutes ago and it fails - "Connection refused"....
Maybe the new fw is the reason.
Will downgrade and test it again - Later….

It still works. The password is unchanged, too.

[Martin72]

aha....

In the prompt, I´ve typed Telnet XXX.XXX.X.XXX and enter...after a few seconds the message appeared witch connection refused (can´t connect to remote host).

[0xdeadbeef]

Why is it then that if the BW restriction is active and significantly higher frequency sine than the limit is connected (let's say 2x the BW) the display cannot be filled vertically with the signal?

I'm not sure if I understand the question. If the bandwidth limit is set to 350MHz and you connect a 700MHz signal, there will still be a sine, but its amplitude will be much lower than expected (way beyond the 3dB point).
Whether you can fill the display or not is a matter of scope settings, but still the amplitude (absolute voltage) of the signal will be too low.

So I've assumed that a pure filtering loss in the analogue side can be compensated with increased gain.

You overlook the frequency dependency. The higher the frequency the smaller the amplitude. Since every signal is composed of a superposition of sinusoidal signals of different frequencies (Fourier series), a bandwidth limitation will remove the amplitude of higher frequency components. I.e. it will remove sharp edges from signals etc.

Another issue is that based on datasheet the afformentioned chip's -3dB point is at 900MHz. A bit low for 1GHz and a bit on the high side for 500MHz.

So what? The variable gain amplifier used in the SDS2000X series had a limit of 750MHz and the scopes were limited to 300MHz. Obviously you don't want the bandwidth of the amplifier to be a major factor in the system bandwidth, so choosing something with roughly twice the bandwidth seems somewhat reasonable.

[edigi]

Whether you can fill the display or not is a matter of scope settings

Nope. With SDS503xX or 505xX there is no such setting if artificial BW limit is exceeded significantly.
Sorry I've realized that I'm in the wrong thread and that has created a confusion.

You overlook the frequency dependency. The higher the frequency the smaller the amplitude. Since every signal is composed of a superposition of sinusoidal signals of different frequencies (Fourier series), a bandwidth limitation will remove the amplitude of higher frequency components. I.e. it will remove sharp edges from signals etc.

I meant and wrote sine, pure sine to be precise.

So what? The variable gain amplifier used in the SDS2000X series had a limit of 750MHz and the scopes were limited to 300MHz. Obviously you don't want the bandwidth of the amplifier to be a major factor in the system bandwidth, so choosing something with roughly twice the bandwidth seems somewhat reasonable.

Sorry wrong thread, my fault, I stop here.

[Tankj]

First post here.

I'm wonder how long that someone will found the silkscreen truth , but no one does yet.

There is no different silkscreen versions at all, the “difference” is just from different channels. Just that simple.

Pics are all from other users under this topic, thanks.

[Martin72]

6) Open a command window on PC, write 'telnet +IP address of your scope'

Can someone try this with the new firmware installed ?
Tried this a few minutes ago and it fails - "Connection refused"....
Maybe the new fw is the reason.
Will downgrade and test it again - Later….

It still works. The password is unchanged, too.

This is what I get:

[jemangedeslolos]

 

[Martin72]

 

Tell me what´s wrong..

[Frex]

I think you must add the telnet port as :
telnet <IP> 5024

Frex

[tv84]

SDS2354X+/SDS2504X+ DESIGNATION MYSTERY    [BUSTED]

Have you ever heard about .CFG files for setting up Siglent HW? 

Those that report a SDS2354X+ possess this sys_cfg.cfg file in the firmdata0:

Code: [Select]

Reversing 1st part of the file [00000000-00000CF7]...
XORing with 0xFF (incrementing pattern)...
XORing with 0xFF from 0x0000067C until 0x00000CF7

00000000 - Main Checksum: FFFFD394 [00000004-00000CF7]  CKSM OK
00000008 - Product_Type: SIGLENT
00000028 - CFG Type: SDS2000X Plus
0000003C - Manufacturer: SIGLENT
00000047 - CML/CNL flag: 0
00000048 - Product_ID: 15100
0000004C - Image Size: 00000000 (0 pixels)
00000050 - USBTMC_Product_IDs: EE39 EE38 EE3A
00000056 - USBTMC_Vendor_ID: F4EC
00000058 - Product Family: SDS
0000005C - Manufacturer_Name: Siglent
0000009C - CFG Flags: 01 01 01 01 00 00 01 00 1800 0B
000000A8 - Model Name 00:
000000B7 - Model Name 01:
000000C6 - Model Name 02:
000000D5 - Model Name 03: SDS2104X Plus
000000E4 - Model Name 04:
000000F3 - Model Name 05: SDS2204X Plus
00000102 - Model Name 06:
00000111 - Model Name 07: SDS2304X Plus
00000120 - Model Name 08:
0000012F - Model Name 09: SDS2074X Plus
00000140 - Model Name 10: SDS2354X Plus
0000014F - Model Name 11: SDS2354X Plus
Those that report a SDS2504X+ possess this sys_cfg.cfg file in the firmdata0:

Code: [Select]

Reversing 1st part of the file [00000000-00000CF7]...
XORing with 0xFF (incrementing pattern)...
XORing with 0xFF from 0x0000067C until 0x00000CF7

00000000 - Main Checksum: FFFFD397 [00000004-00000CF7]  CKSM OK
00000008 - Product_Type: SIGLENT
00000028 - CFG Type: SDS2000X Plus
0000003C - Manufacturer: SIGLENT
00000047 - CML/CNL flag: 0
00000048 - Product_ID: 15100
0000004C - Image Size: 00000000 (0 pixels)
00000050 - USBTMC_Product_IDs: EE39 EE38 EE3A
00000056 - USBTMC_Vendor_ID: F4EC
00000058 - Product Family: SDS
0000005C - Manufacturer_Name: Siglent
0000009C - CFG Flags: 01 01 01 01 00 00 01 00 1800 0B
000000A8 - Model Name 00:
000000B7 - Model Name 01:
000000C6 - Model Name 02:
000000D5 - Model Name 03: SDS2104X Plus
000000E4 - Model Name 04:
000000F3 - Model Name 05: SDS2204X Plus
00000102 - Model Name 06:
00000111 - Model Name 07: SDS2304X Plus
00000120 - Model Name 08:
0000012F - Model Name 09: SDS2074X Plus
00000140 - Model Name 10: SDS2354X Plus
0000014F - Model Name 11: SDS2504X Plus

See the difference?        It seems Siglent, at the beginning, was shipping the 1st file. After some months it changed to the 2nd one.

Solution:
- Replace the file (via linux) and the scope automatically will assume the new setting after reboot. TESTED OK

Attached is the file of a SDS2504X+.

Now you can all stop discussing this BW thing and move on!

[Elasia]

Copy paste error

I was wondering as such or similar bug, thanks tv

Also im assuming no serialization in that config file ;p

[KeBeNe]

SDS2354X Plus to a SDS2504X Plus. (Sys-Info Mod)

first, enable telnet: create a file named as 'siglent_device_startup.sh', content 'telnetd'
then copy sys_cfg.cfg to usb drive
telnet user name 'root'
password "siglent_sds1000x_e"
mount -o remount,rw,sync /usr/bin/siglent/firmdata0

cp -R /usr/bin/siglent/usr/mass_storage/U-disk0/sys_cfg.cfg /usr/bin/siglent/firmdata0

[jemangedeslolos]

Tell me what´s wrong..

Sorry Martin, I was just refering to the Tankj post.
He puts his finger on the fact that there is actually no difference in the silkscreen....so 3 pages for nothing 

Don't know what is going wrong with your telnet session.

A user encountered a problem after firmware update on the webserver ( white page instead of the scope screen )
Updating the firmware a second time and the problem was gone. Maybe you can try to update once again ?

[tv84]

He puts his finger on the fact that there is actually no difference in the silkscreen....so 3 pages for nothing 

I also loved it! 

[Martin72]

Sometimes, things could get very easy...

Deskew Fixture:

Contact siglent.eu what my buyed item concerns, when it will arrive…
Probably next week, they don´t got it in stock.

[2N3055]

SDS2354X+/SDS2504X+ DESIGNATION MYSTERY    [BUSTED]...

 

[stafil]

Siglent engineers must be trolling us

Great job tv84. Upgraded mine to SDS2754X+ 

[Martin72]

Tadaa…

Thanks to KeBeNe and the special one….