Siglent will release the SDS2000X-E on 10th December.
Will come in two flavors, 200MHz and 350MHz...
What are the main differences for the 1000X-E?
What are the main differences for the 1000X-E?It is better imagine it is more like half channel SDS1004X-E mutation- evolution (lot of similarities except BW samplerate and due to double samplerate memory is doubled so it is proportionally same.)
You need split thinking to two separate pathway.
SDS1002X-E
SDS1004X-E
Even when SDS2xx2X-E is 2 channel it is not evolution of SDS1002X-E
I don't find it bad. It widens the entry portfolio.
I'm waiting for the SDS5000 but now there are also the Rigols...
I thought I should back up my claims by showing an example:
Square 100MHz_Z2ns+FFT
This is a 100MHz square wave with <<100ps transition time.
Main timebase is 100ns/div in order to get a sufficiently detailed FFT from DC to 2GHz.
Zoom timebase is 2ns/div in order to get a detailed Y-t view.
Automatic measurements:
FOV = Overshoot after a falling edge.
ROV = Overshoot after a rising edge.
Rise & Fall times are not accurate because of limited scope rise time and also time measurement resolution limited to 20ps at that timebase.
no 4 channel model because?
Are the MSO/LA signals available via LXI/SCPI?
Is serial decode still restricted to just what is on screen?
The 2000X series scope is a bit hobbled by the fact that the logic analyzer (digital signals, serial decoders) is not exposed via SCPI.
All info is now available:
https://www.siglentamerica.com/digital-oscilloscopes/sds2000x-e/
Options
16ch MSO
Are the MSO/LA signals available via LXI/SCPI?They are in the current 2kX programming guide:
https://www.siglentamerica.com/wp-content/uploads/dlm_uploads/2017/10/Programming-Guide-1.pdf
P58
All info is now available:
https://www.siglentamerica.com/digital-oscilloscopes/sds2000x-e/
Options
16ch MSO
Maybe I'm missing it and it's in plain sight, but what is the sample rate on the digital channels?
Are the MSO/LA signals available via LXI/SCPI?They are in the current 2kX programming guide:
https://www.siglentamerica.com/wp-content/uploads/dlm_uploads/2017/10/Programming-Guide-1.pdf
P58Thanks for sending that. It has been a while since I looked for an update to the SCPI manual. I also see that I have missed a couple firmware updates in the past year.
It says "D[X] — Digital channel. Only valid for SDS1000X-E series." (Page 179, WAVEFORM command.) Yes, one can control the MSO, but the digital waveforms cannot be retrieved from a 2000X for external analysis. This means that only the 4 analog waveforms can be used in tools like sigrok -- and, as a 2000X owner, that makes me sad.
But that's certainly good news for the 1000X-E users. And hopefully that means it works on the 2000X-E series as well.
Check:
Read Waveform Data of Digital Example
P251
Will that work for you ?
Check:
Read Waveform Data of Digital Example
P251
Will that work for you ?
Does that work for you on a 2000X?
It's in the datasheet: P3 and 14.
Maximum waveform capture rate up to 1GSa/s, Record length up to 14 Mpts/CH
https://www.siglentamerica.com/wp-content/uploads/2018/12/SDS2000X-E_DataSheet_DS0102E-E01A.pdf
The 16 digital channels are provided with an external module, the same as used for SDS1004X-E models, the SLA1016 that connects into the front Sbus connector.
https://www.siglentamerica.com/accessory/sla1016/
It's in the datasheet: P3 and 14.
Maximum waveform capture rate up to 1GSa/s, Record length up to 14 Mpts/CH
https://www.siglentamerica.com/wp-content/uploads/2018/12/SDS2000X-E_DataSheet_DS0102E-E01A.pdf
The 16 digital channels are provided with an external module, the same as used for SDS1004X-E models, the SLA1016 that connects into the front Sbus connector.
https://www.siglentamerica.com/accessory/sla1016/
Thanks you. I'm considering something like this as a second MSO.
Sold mine.
(Replacing with a SDS5kX soon )
Sold mine.
(Replacing with a SDS5kX soon )
Do you mean DS5k from Rigol, or will there be SDS5kX soon from Siglent?
Are you carrying nay Demo Units while you are in WA?
http://codelabs.ru/firmware/siglent/sds2000x-e/official/1.1.20R3/
19/03/2021 13:50:02 82602724 [00156717-005D5F34] sds1000b.app
19/08/2019 18:08:06 073A3093 [00163D5A-005E1B47] sds1000b.app
17/08/2018 17:40:11 500FAC1D [00803DA3-0080BAB9] top_acq_fpga.bit
30/11/2020 09:19:13 7C7B7398 [0080E942-008157E0] top_acq_fpga.bit
12/08/2019 18:47:20 105E9AEF [00000069-0016158F] top_sds2000x_e_fpga.bit
18/03/2021 09:00:18 0DE50569 [00000069-00153F4C] top_sds2000x_e_fpga.bit
15/08/2019 11:30:21 BCA6A646 [00695A9E-006975EC] ui_data/arabic_text_info.xml
25/11/2020 16:36:12 988957D4 [0068A522-0068C084] ui_data/arabic_text_info.xml
22/07/2019 10:22:28 F80642D3 [00661F53-00665369] ui_data/english_help_info.xml
25/11/2020 16:36:13 4188EC72 [00656356-00659735] ui_data/english_help_info.xml
15/08/2019 11:30:20 A0CA22D3 [00676BDA-00678742] ui_data/english_text_info.xml
25/11/2020 16:36:12 46EF2F58 [0066B604-0066D17E] ui_data/english_text_info.xml
15/08/2019 11:30:20 4D4CC7DE [006C0AD7-006C265E] ui_data/french_text_info.xml
25/11/2020 16:36:11 1938CE93 [006B55A6-006B7145] ui_data/french_text_info.xml
15/08/2019 11:30:20 E913CA3C [00660398-00661F17] ui_data/italian_text_info.xml
25/11/2020 16:36:12 197C678B [00654785-0065631A] ui_data/italian_text_info.xml
15/08/2019 11:30:20 A0CA22D3 [006687F3-0066A35B] ui_data/japanese_text_info.xml
25/11/2020 16:36:13 1EC3EBD1 [0065CBBF-0065E73A] ui_data/japanese_text_info.xml
15/08/2019 11:30:21 A0CA22D3 [00683B82-006856EA] ui_data/korean_text_info.xml
25/11/2020 16:36:12 820AA2AD [006785DF-0067A15A] ui_data/korean_text_info.xml
22/07/2019 10:22:28 25C950F8 [0067378D-00676B9E] ui_data/portuguese_help_info.xml
25/11/2020 16:36:12 C693D355 [00667B6C-0066B5C8] ui_data/portuguese_help_info.xml
15/08/2019 11:30:20 80400B18 [006B4C15-006B679C] ui_data/portuguese_text_info.xml
25/11/2020 16:36:11 19001581 [006A96DE-006AB27A] ui_data/portuguese_text_info.xml
15/08/2019 14:52:17 BA26AB00 [006AFDEA-006B1CDE] ui_data/russian_text_info.xml
25/11/2020 16:36:13 D53886C8 [006A489E-006A67A7] ui_data/russian_text_info.xml
22/07/2019 10:22:29 5C36A722 [006AC754-006AFDAE] ui_data/simp_help_info.xml
25/11/2020 16:36:13 CF0A1790 [006A1210-006A4862] ui_data/simp_help_info.xml
15/08/2019 11:30:20 E356D421 [006AAA7F-006AC71B] ui_data/simp_text_info.xml
25/11/2020 16:36:11 9CAEF00B [0069F51C-006A11D7] ui_data/simp_text_info.xml
15/08/2019 11:30:20 364466B7 [0068D77D-0068F305] ui_data/spanish_text_info.xml
25/11/2020 16:36:12 6E9E9F6C [006821ED-00683D89] ui_data/spanish_text_info.xml
22/07/2019 10:22:29 28AB5506 [006B9804-006BCEB9] ui_data/trad_help_info.xml
25/11/2020 16:36:13 CF9CC21D [006AE2E2-006B1988] ui_data/trad_help_info.xml
12/03/2021 09:51:01 252D17C4 [0068C0BD-0068F33C] ui_data/trad_menu_info.xml
22/07/2019 10:22:28 50B7FBEE [00697625-0069A89F] ui_data/trad_menu_info.xml
15/08/2019 11:30:21 314D63E0 [0067EBF0-00680905] ui_data/trad_text_info.xml
25/11/2020 16:36:12 4ACF25EA [0067362C-00675362] ui_data/trad_text_info.xml
16/07/2018 16:54:16 E23B57EF [007D0479-007D5F3D] www/BinToCSV_tool.zip
24/12/2019 09:26:27 9D21FF8B [007CB3F5-007D2672] www/BinToCSV_tool.zip
14/07/2018 15:16:18 BDD7A20C [007597CD-0075A1BF] www/Instrument/novnc/include/base.css
29/04/2020 14:25:11 511068CF [0074E289-0074EC5B] www/Instrument/novnc/include/base.css
14/07/2018 15:16:18 0177A851 [007565D8-00756FDA] www/Instrument/novnc/include/base_mobile.css
29/04/2020 14:25:04 98A0800A [0074B0B6-0074BA96] www/Instrument/novnc/include/base_mobile.css
16/12/2019 14:53:28 4928B944 [007960B5-00798A3F] www/Instrument/novnc/vnc_auto.php
23/04/2019 16:26:22 F6DAD5CC [007A1619-007A3C55] www/Instrument/novnc/vnc_auto.php
06/12/2019 10:45:29 D4DFFF19 [006B76DE-006B7C0B] www/SCPI_control.php
13/07/2018 10:21:01 F7CB535A [006C2BE8-006C312E] www/SCPI_control.php
13/07/2018 10:21:01 DA06DD28 [007CEB1A-007CF178] www/css/device/device_control.css
29/04/2020 14:24:16 DB820B52 [007C3BE0-007C4228] www/css/device/device_control.css
06/12/2019 10:45:27 BF3A0A0E [007C35EA-007C3B73] www/css/welcome.css
13/07/2018 10:21:01 26D75603 [007CE536-007CEAAD] www/css/welcome.css
06/12/2019 10:45:28 7615EC62 [007D867E-007E6AB0] www/img/oem_logo.png
29/04/2020 14:24:29 BA4681C7 [0079AAE0-0079DD60] www/js/device/t_table.js
31/08/2018 10:44:22 BCC6B03D [007A5CF6-007A8EC3] www/js/device/t_table.js
13/07/2018 10:21:04 D03B120A [007B5103-007B53DB] www/js/home_info.js
16/12/2019 14:26:11 C992D686 [007A9FCB-007AA2E9] www/js/home_info.js
16/12/2019 14:53:28 3B557077 [007A4533-007A51F6] www/js/lan_config.js
31/08/2018 10:44:22 85C57E94 [007AF696-007B0327] www/js/lan_config.js
06/12/2019 10:45:28 577E70AE [007BA347-007BA54E] www/js/log_in.js
13/07/2018 10:21:04 872B6CB6 [007C5439-007C549A] www/js/log_in.js
06/12/2019 10:45:29 1873D146 [007A8E3D-007A9A1C] www/js/main.js
13/07/2018 10:21:04 A11D7515 [007B3F6E-007B4B54] www/js/main.js
06/12/2019 10:45:28 FAE6C4E1 [006B7C35-006B82C0] www/lan.php
13/07/2018 10:21:03 7F4DEC6B [006C3158-006C37E2] www/lan.php
06/12/2019 10:45:28 50415BFD [007D26A4-007D2FA5] www/lan_setting.php
13/07/2018 10:21:03 CB8B927E [007D5F6F-007D686B] www/lan_setting.php
04/12/2019 17:22:06 56E1BBCB [007CA44C-007CB23D] www/lighttpd.conf
06/12/2019 10:45:28 A93CF140 [007C49EC-007C4FC3] www/login.php
31/08/2018 10:44:21 A84261DE [007CF93C-007CFF09] www/login.php
04/12/2019 17:22:07 02397584 [007C53A5-007CA41C] www/php.ini
08/04/2020 10:34:20 A99B4633 [006B7195-006B76AB] www/welcome.php
13/07/2018 10:21:01 0C3FC166 [006C26AE-006C2BB5] www/welcome.php
There is also firmware version 1.1.20R3 (that my SDS2000X-E came with). Its being said to be the intermediate version that was created "to optimize the internal processes" (refactoring?) without any (hmm, may be yes, may be not bug fixes/new issues. And also "... as praparations for the further improvements" was mentioned, so it could be that the new firmware for SDS2000X-E could appear at some point at the Siglent download areas.
Since new devices come with it, I consider it to be stable enough for keen engineers to try it. It came from Siglent representatives, but just as a lone .ADS file, not the usual zip with changelogs.
http://codelabs.ru/firmware/siglent/sds2000x-e/official/1.1.20R3/
After so many months and in the presence of bugs, the official downloadable FW release for the SDS2202X-E is still stuck at 1.1.19R5, while new models are sold with newer versions. Version 1.1.20R3 was available AT LEAST from last june and thanks to user rea I could install it on last september.
But why don't they distribute updates? Perhaps tautech can help?
20R3 is still the current version as I got a copy just recently.
20R3 is still the current version as I got a copy just recently.
Thank you for your answer, tautech.
Good to know that 20R3 is still the current version, but why don't they publish it? If they distribute it, it must be tested and official.
Probably as they're still working on it as I believe R3 was built to fix this issue:
https://www.eevblog.com/forum/testgear/sds2202x-e-calibrate-signal-problems-on-ch1/
It seems a firmware upgrade put the scope out of whack although I have not experienced in any of the firmware installs we often do.
Successfully applied hack to transform the SDS2202X-E to 2352X-E, thanks to information in the blog!
Successfully applied hack to transform the SDS2202X-E to 2352X-E, thanks to information in the blog!
After PM from one user, I realized that a detailed upgrade procedure wasn't available. So I am attaching a suitable Python 3 script, containing instructions.
I used only '300' option.
So you used the "300M" option to get the upgrade to 2352X-E with 350MHz bandwidth?
If possible, could you check what your scope is displaying as "Product Type" in (press Utility button) > "System Status" menu after applying this patch?
What is the model reported by *IDN? SCPI command?
Thank you, that's very helpful. I made a silly mistake of using the code for "350M" and now the scope has a blank field in place of its Product Type. Huh.... I wonder if it's possible to remove a license code...
Spotted an update for these today.....finally the mystical version 20R3 !
https://int.siglent.com/upload_file/zip/firmware/Oscilloscope/SDS2000X-E_V1.1.20R3_EN.zip
8.4MB
The release notes only mention compatibility for later HW versions.