Siglent SDS6000A DSO's 500MHz-2GHz

[tv84]

Taken from SDS6000 FW package. It seems the bitstreams are made by LeCroy.

Is that a bad thing? 

Not at all. One thing I learned in this forum is that having a LeCroy badge is .

[mubes]

I think a real benefit would be if they develop some sort of interface where we can add our own
decoders. Imagine a github depository with hundreds or even thousands of protocols !!!
In the long term, it would be less work for Siglent, and a great benefit for all of their users ...

rudi

Rudi,

Worth looking at ScopeHal (https://github.com/azonenberg/scopehal-apps), which pretty much does what you want.  I used it a lot on SDS2104X for SWD analysis while bringing up some new arm debug probes.

DAVE

[tautech]

New firmware for SDS6000A models.

Version V1.4.0.0
https://int.siglent.com/upload_file/zip/firmware/Oscilloscope/SDS6000_V1.4.0.0_EN.zip
122 MB

Release notes
Channel: two custom probe ratio options supported
Fixed several bugs
Bode Plot draw error (missing draw)
Bode Plot - Very slow, nearly stuck, with some signal levels
Counter - totalizer not showing all numbers
Counter (time period) shows incredible numbers

[tautech]

First impressions are a jet aircraft taking off  then the fan throttles back to be surprisingly quiet. 
Found a bug in the time set menu where if set by location takes no account for DST despite entering the correct time. Nope, user error. 

Tv84 happy to purchase one for a play date if you wish 

Save the date!

Screenshot FYI 

[rf-loop]

First impressions are a jet aircraft taking off  then the fan throttles back to be surprisingly quiet. 
Found a bug in the time set menu where if set by location takes no account for DST despite entering the correct time. Nope, user error. 

Tv84 happy to purchase one for a play date if you wish 

Save the date!

Screenshot FYI 

Nice, you get The Oscilloscope.

[tv84]

Screenshot FYI 

Which FW version is in the machine?

[tautech]

Nice, you get The Oscilloscope.

The Oscilloscope it really is as it's full of tricks as you well know. 

A couple of screenshots of Leo's 30ps pulser and the only changes were made to memory handling in the Acquisition menu. The best of all worlds. 

Screenshot FYI 

Which FW version is in the machine?

Came with the latest public version now further updated and currently running Autocal.

[hpw]

@tautech

please do the same using the fastest resolution... may 500ps..50ps time base.. so only one rising edge..

[tautech]

@tautech

please do the same using the fastest resolution... may 500ps..50ps time base.. so only one rising edge..

Sure, here you go. (Fixed mem depth)

Edit to add another with Auto mem management engaged.

[hpw]

@tautech: Are you using an 30 or 50ps fast pulse?? Also do not like much the overshoots..

[tv84]

FPGA's inside:

acq1_2G_Z.bin / acq1_2G_ZC.bin  use a IDCode = 04A59093 (anyone knows this device?) 
LeCroyZD.bin uses IDCode = 04002093  (Xilinx XC6SLX16)

Code: [Select]

MASTER_ACQ_FPGA  - /usr/bin/siglent/config/fpga/acq1_2G_LPM.bin  (Board Type = 2)
SLAVE_ACQ_FPGA   - /usr/bin/siglent/config/fpga/acq1_2G_LPS.bin  (Board Type = 3)
ACQ1_NEW_FPGA    - /usr/bin/siglent/config/fpga/acq1_2G_ZC.bin
ACQ1_FPGA        - /usr/bin/siglent/config/fpga/acq1_2G_Z.bin
MST_FPGA         - /usr/bin/siglent/config/fpga/mst_Z.bin
AWG_FPGA         - /usr/bin/siglent/config/fpga/awg_Z.bin
MAP_FPGA         - /usr/bin/siglent/config/fpga/LeCroyZD.bin

Code: [Select]

Partition Map for MMC device 1  --   Partition Type: EFI         (Each LBA = 0x200 bytes)

Part    Start LBA       End LBA      Size       Name             
  1     0x00000100      0x000002ff   00000200   "mlo"           
  2     0x00000300      0x00000fff   00000D00   "uboot"         
  3     0x00001000      0x000017ff   00000800   "devicetree"     
  4     0x00001800      0x00003fff   00002800   "oem"           
  5     0x00004000      0x000047ff   00000800   "lcd"           
  6     0x00004800      0x0000efff   0000A800   "kernel"         
  7     0x0000f000      0x00072fff   00064000   "reserved1"     
  8     0x00073000      0x001d0fff   0015E000   "rootfs"         
  9     0x001d1000      0x001dafff   0000A000   "firmdata0"     
 10     0x001db000      0x001dd7ff   00002800   "caldata"       
 11     0x001dd800      0x0024b7ff   0006E000   "siglent"       
 12     0x0024b800      0x0064b7ff   00400000   "datafs"         
 13     0x0064b800      0x00747fde   000FC7DF   "reserved2"

Code: [Select]

Filesystem                Size      Used Available Use% Mounted on
/dev/root               673.0M    580.8M     43.2M  93% /
devtmpfs                  1.4G      4.0K      1.4G   0% /dev
tmpfs                     1.9G     12.0K      1.9G   0% /dev/shm
tmpfs                     1.9G     17.5M      1.9G   1% /run
tmpfs                     1.9G         0      1.9G   0% /sys/fs/cgroup
tmpfs                     1.9G     24.0K      1.9G   0% /tmp
tmpfs                    16.0M         0     16.0M   0% /media/ram
tmpfs                    50.0M    584.0K     49.4M   1% /var/volatile
/dev/mmcblk1p11         197.1M    122.1M     59.6M  67% /usr/bin/siglent
/dev/mmcblk1p9           18.4M    379.0K     16.6M   2% /usr/bin/siglent/firmdata0
/dev/mmcblk1p10           3.8M     33.0K      3.5M   1% /usr/bin/siglent/firmdata1
/dev/mmcblk1p12           1.9G      4.0M      1.8G   0% /usr/bin/siglent/usr
/dev/mmcblk1p13         481.0M      2.3M    449.5M   1% /ota
/dev/sda1                 3.6G    192.0K      3.6G   0% /usr/bin/siglent/usr/mass_storage/U-disk0
Parsing of sys_cfg.cfg:

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: FFFFE333 [00000004-00000CF7]  CKSM OK
00000008 - Product_Type: SIGLENT
00000028 - CFG Type: SDS6000
0000003C - Manufacturer_Name: SIGLENT
00000047 - CFG Flag_LongMemory: 00
00000048 - Product_ID: 15100
0000004C - Logo Image Size: 00000000 (0 pixels)
00000050 - USB_Prod_ID_PTP: EE39
00000052 - USB_Prod_ID_RAW: EE38
00000054 - USB_Prod_ID_TMC: EE3A
00000056 - USB_Vendor_ID: F4EC
00000058 - Prefix: SDS
0000005C - Logo_Manufacturer: Siglent
0000009C - CFG Flag_pic_machine: 01
0000009D - CFG Flag_sys_machine: 01
0000009E - CFG Flag_____USB_TMC: 01
0000009F - CFG Flag___SCPI/ERES: 01
000000A0 - CFG Fl_invert/neuter: 00
000000A1 - CFG Flag___skew/gate: 00
000000A2 - CFG Flag____vxi/roll: 01
000000A3 - CFG Flag___________A: 00    not_used(?)
000000A4 - CFG Flag___lang_mask: 0000
000000A6 - CFG Flag__lang_total: 13
000000A7 - CFG Flag_mach_series: 00
000000A8 - Machine Name  20 MHz:
000000B7 - Machine Name  40 MHz:
000000C6 - Machine Name  60 MHz:
000000D5 - Machine Name 100 MHz:
000000E4 - Machine Name 150 MHz:
000000F3 - Machine Name 200 MHz:
00000102 - Machine Name 250 MHz:
00000111 - Machine Name 300 MHz:
00000120 - Machine Name  50 MHz:
0000012F - Machine Name  70 MHz:
0000013E - CFG Flag___BW_change: 01
0000013F - CFG Flag_hide_set_BW: 01
00000140 - Machine Name 350 MHz: SDS6034A
0000014F - Machine Name 500 MHz: SDS6054A
0000015E - Machine Name 750 MHz:
0000016D - Machine Name1000 MHz: SDS6104A
0000017C - Machine Name2000 MHz: SDS6204A

telnet password:
root:$6$Y62LU2y.lvnI6m6r$Sp7/1zAtiLnyzmE8nSfyYJHlvVcSlkCEBY54xFFfvGQHNiHOCmNir5/M0SpZ9YvKSsewymxWYLKvCaYqgsO/W1:18389:0:99999:7:::

[tautech]

@tautech: Are you using an 30 or 50ps fast pulse?? Also do not like much the overshoots..

30ps Leo Bodnar pulser.
Some overshoot visible in its test screenshot.

[nctnico]

There is no edge on the top graph. the amplitude is really low and the overshoot/undershoot values look weird. On the bottom graph (also 50ps /div?) the edge fall time isn't at sub-ps levels either. The risetime of the SD-30 sampling head is around 9ps. IOW: those sub-ps numbers look like a measurement error to me.

[mawyatt]

Sub-Picoseconds!! That implies THz performance 

Best,

[2N3055]

In attachment cal  sheet for my pulser

[nctnico]

Even Leo can have a bad day I guess 

[Martin72]

In attachment cal  sheet for my pulser

I only got two x-times folded papers to fit in the tiny package - Did I miss a pdf version from it.....

[tv84]

I only got two x-times folded papers to fit in the tiny package - Did I miss a pdf version from it.....

Sinisa digitsed his. I also got 2 pieces of paper.

[tautech]

From another thread:

Any chance you could show the 10 bit and various ERES modes with this new scope?

No 10 bit mode or ERES in 6000A, but an 8 additional bits of Hi-Res is what these offer and it's back in the Acquire menu with its button very conveniently placed directly below the timebase encoder.

Signals from STB3, PWM and last 2 pics DPO test signals.
Scope SDS6204A FW 4.0
Supplied 500 MHz SP3050A compact probe.

All relevant scope settings visible in menus.

[tautech]

2 more pics with Gnd input coupling.

[cgroen]

tautech,
I ordered a pulser from Leo 2 days ago, I will do the same measurements when my SDS6204 arrives (looks nice!).

[tautech]

tautech,
I ordered a pulser from Leo 2 days ago, I will do the same measurements when my SDS6204 arrives (looks nice!).

Mine was only a couple of weeks from UK to NZ.
I didn't get it for this stuff so much as I have RF sources to 3.2 GHz for testing BW etc but instead I have a plan to check a range of probes against Siglent probes and step response tests will be part of that.
Now I finally have a pretty fast scope yet I'm still becoming familiar with it the winters days coming will be a good opportunity to finally get onto this project I've been wanting to do although the heat is off some now Siglent have revised pricing on their passive probes.
You should be impressed with the SP3050A probes.....and your new scope. 

[mawyatt]

@tautech,

Thanks, looks good 

If you have a chance, what's the pulse rise time look like with the various ERES? This should give a good indicator of BW with ERES modes.

Best,

[tautech]

If you have a chance, what's the pulse rise time look like with the various ERES? This should give a good indicator of BW with ERES modes.

Kinda tricky as we only have Hi-Res. 

After many many tries with all modes of which there would be too many screenshots to post the best/fastest risetimes were measured with these settings:
ESR = ON
Peak Detect or Normal acquisition
Mem Management = Auto

The addition of Hi-Res limits channel mem depth to 12.5 Mpts.
Hi-Res 4 bits pushes out risetimes to 1.3 ns from ~245ps

Examination of risetime screenshots in above posts displays the settings that provide the cleanest races with least digitization noise are in Fixed Mem mode such as the one below although the measured risetimes are just a couple of ps longer than in Auto Mem mode.

Still getting used to this scope and already I have a preference to use it in Fixed Mem mode, not for the new feature that will become evident in time  but for the nice fine traces it displays.

[nctnico]

Still getting used to this scope and already I have a preference to use it in Fixed Mem mode,

I can't help it but I'm having an 'I told you so moment'.