EEVblog Electronics Community Forum
Products => Test Equipment => Topic started by: miyagi on May 28, 2020, 01:17:58 am
-
Thank you for some members, there is a quick and easy way to hack Siglent SDS2000X Plus. I open this dedicated post for new owners of SDS2000X+, who may want to hack it. And if there will be some changes of the hack method, we can also discuss at here.
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3040998/#msg3040998 (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3040998/#msg3040998)
Kengen link
https://repl.it/repls/DirectProbableTwintext (https://repl.it/repls/DirectProbableTwintext)
-
Hi,
I´ll take this to my Threadlist....
Martin
-
I just dumped the Linux boot:
Start menu vdma ...
Config AXI VDMA...
Start menu vdma done.
U-Boot 2014.07-svn72330 (Aug 06 2019 - 22:37:18)
Board: Xilinx Zynq
I2C: ready
DRAM: ECC disabled 496 MiB
NAND: 256 MiB
MMC: zynq_sdhci: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
int board_late_init(void)+++++
[INFO]int fb_display_logo(void)++++++++++++
[INFO]pStorageMem=0x1fa00000, logo_data=0x200036, width=1024, height=600
[INFO]int fb_display_logo(void)----------
int board_late_init(void)-----
Net: Gem.e000b000
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
USB1: ULPI request timed out
zynq ULPI viewport init failed
lowlevel init failed
scanning usb for storage devices... 0 Storage Device(s) found
Copying Linux from USB to RAM...
** Bad device usb 0 **
** Bad device usb 0 **
Copying Linux from NAND flash to RAM...
NAND read: device 0 offset 0x780000, size 0x400000
4194304 bytes read: OK
NAND read: device 0 offset 0xb80000, size 0x80000
524288 bytes read: OK
## Booting kernel from Legacy Image at 02080000 ...
Image Name: Linux-3.19.0-01-svn165603
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3713480 Bytes = 3.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
Booting using the fdt blob at 0x2000000
EHCI failed to shut down host controller.
Loading Kernel Image ... OK
Loading Device Tree to 1dd0d000, end 1dd13e1b ... OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.19.0-01-svn165603 (xielindong@david-virtual-machine) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-50) ) #192 SMP PREEMPT Tue Aug 6 23:16:29 CST 2019
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Zynq Zed Development Board
[ 0.000000] cma: Reserved 16 MiB at 0x1e000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] PERCPU: Embedded 9 pages/cpu @5dfd0000 s8128 r8192 d20544 u36864
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 125984
[ 0.000000] Kernel command line: console=ttyPS0,115200 root=/dev/mtdblock5 rootfstype=cramfs init=/linuxrc earlyprintk uboot_version=05
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 479828K/507904K available (4638K kernel code, 234K rwdata, 1800K rodata, 200K init, 223K bss, 11692K reserved, 16384K cma-reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0x5f800000 - 0xff000000 (2552 MB)
[ 0.000000] lowmem : 0x40000000 - 0x5f000000 ( 496 MB)
[ 0.000000] pkmap : 0x3fe00000 - 0x40000000 ( 2 MB)
[ 0.000000] modules : 0x3f000000 - 0x3fe00000 ( 14 MB)
[ 0.000000] .text : 0x40008000 - 0x40651d7c (6440 kB)
[ 0.000000] .init : 0x40652000 - 0x40684000 ( 200 kB)
[ 0.000000] .data : 0x40684000 - 0x406beae0 ( 235 kB)
[ 0.000000] .bss : 0x406beae0 - 0x406f6a44 ( 224 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C-310 erratum 769419 enabled
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 ID prefetch enabled, offset 1 lines
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
[ 0.000000] slcr mapped to 5f804000
[ 0.000000] zynq_clock_init: clkc starts at 5f804100
[ 0.000000] Zynq clock init
[ 0.000010] sched_clock: 64 bits at 383MHz, resolution 2ns, wraps every 2868291043328ns
[ 0.000117] timer #0 at 5f806000, irq=17
[ 0.000446] Console: colour dummy device 80x30
[ 0.000464] Calibrating delay loop... 1528.62 BogoMIPS (lpj=7643136)
[ 0.090219] pid_max: default: 32768 minimum: 301
[ 0.090357] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090370] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090945] CPU: Testing write buffer coherency: ok
[ 0.091135] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.091208] Setting up static identity map for 0x45fe58 - 0x45feb0
[ 0.190210] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.190281] Brought up 2 CPUs
[ 0.190298] SMP: Total of 2 processors activated (3057.25 BogoMIPS).
[ 0.190306] CPU: All CPU(s) started in SVC mode.
[ 0.190776] devtmpfs: initialized
[ 0.191512] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.196761] NET: Registered protocol family 16
[ 0.198696] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.221112] cpuidle: using governor ladder
[ 0.251082] cpuidle: using governor menu
[ 0.258643] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.258658] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.258787] zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0x5f880000
[ 0.275148] vgaarb: loaded
[ 0.275558] SCSI subsystem initialized
[ 0.275939] usbcore: registered new interface driver usbfs
[ 0.276022] usbcore: registered new interface driver hub
[ 0.276103] usbcore: registered new device driver usb
[ 0.276247] phy0 supply vcc not found, using dummy regulator
[ 0.276333] phy1 supply vcc not found, using dummy regulator
[ 0.276444] --------------usb_udc_init ------
[ 0.276686] pps_core: LinuxPPS API ver. 1 registered
[ 0.276696] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti[member=183778]linux[/member].it>
[ 0.276742] PTP clock support registered
[ 0.276982] EDAC MC: Ver: 3.0.0
[ 0.278788] Switched to clocksource arm_global_timer
[ 0.278832] cfg80211: Calling CRDA to update world regulatory domain
[ 0.289700] NET: Registered protocol family 2
[ 0.290403] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.290475] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.290565] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.290611] TCP: reno registered
[ 0.290626] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.290655] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.290856] NET: Registered protocol family 1
[ 0.291161] RPC: Registered named UNIX socket transport module.
[ 0.291172] RPC: Registered udp transport module.
[ 0.291180] RPC: Registered tcp transport module.
[ 0.291186] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.291580] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 0.292801] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.294327] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.294464] fuse init (API version 7.23)
[ 0.295456] io scheduler noop registered
[ 0.295473] io scheduler deadline registered
[ 0.295519] io scheduler cfq registered (default)
[ 0.297397] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.297415] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.297877] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 146, base_baud = 6249999) is a xuartps
[ 0.880719] console [ttyPS0] enabled
[ 0.884857] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to 5f878000
[ 0.891560] [drm] Initialized drm 1.1.0 20060810
[ 0.903247] brd: module loaded
[ 0.909902] loop: module loaded
[ 0.917058] libphy: MACB_mii_bus: probed
[ 0.998878] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 149 (00:0a:35:00:01:22)
[ 1.008750] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:1e, irq=-1)
[ 1.020233] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.026684] ehci-pci: EHCI PCI platform driver
[ 1.031266] usbcore: registered new interface driver usbtmc
[ 1.036836] usbcore: registered new interface driver usb-storage
[ 1.042972] e0002000.usb supply vbus not found, using dummy regulator
[ 1.049670] ci_hdrc ci_hdrc.0: EHCI Host Controller
[ 1.054482] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
[ 1.078756] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
[ 1.084216] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.090950] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.098125] usb usb1: Product: EHCI Host Controller
[ 1.103000] usb usb1: Manufacturer: Linux 3.19.0-01-svn165603 ehci_hcd
[ 1.109508] usb usb1: SerialNumber: ci_hdrc.0
[ 1.114417] hub 1-0:1.0: USB hub found
[ 1.118111] hub 1-0:1.0: 1 port detected
[ 1.122498] e0003000.usb supply vbus not found, using dummy regulator
[ 1.130731] mousedev: PS/2 mouse device common for all mice
[ 1.136240] <<-GTP-INFO->> GTP driver installing...
[ 1.141305] i2c /dev entries driver
[ 1.146712] rtc-ds1307 0-0068: rtc core: registered ds1340 as rtc0
[ 1.153387] <<-GTP-INFO->> GTP Driver Version: V2.4<2014/11/28>
[ 1.159240] <<-GTP-INFO->> GTP Driver Built@23:12:41, Aug 6 2019
[ 1.165296] <<-GTP-INFO->> GTP I2C Address: 0x14
[ 1.169972] 0-0014 supply vdd_ana not found, using dummy regulator
[ 1.176101] 0-0014 supply vcc_i2c not found, using dummy regulator
[ 1.182304] <<-GTP-INFO->> Guitar reset
[ 1.309207] <<-GTP-INFO->> IC Version: 928_1060
[ 1.314287] <<-GTP-INFO->> Sensor_ID: 0
[ 1.318040] <<-GTP-ERROR->> Failed to parse config data form device tree.
[ 1.324906] <<-GTP-ERROR->> GTP init panel failed.
[ 1.329635] <<-GTP-INFO->> create proc entry gt9xx_config success
[ 1.335901] input: goodix-ts as /devices/virtual/input/input0
[ 1.341791] <<-GTP-INFO->> GTP works in interrupt mode.
[ 1.346948] cdns-i2c e0004000.i2c: 400 kHz mmio e0004000 irq 144
[ 1.353696] lm75 0-0048: hwmon0: sensor 'adt75'
[ 1.359194] zynq-edac f8006000.memory-controller: ecc not enabled
[ 1.365373] Xilinx Zynq CpuIdle Driver started
[ 1.370301] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.376485] usbcore: registered new interface driver usbhid
[ 1.382096] usbhid: USB HID core driver
[ 1.385962] usbcore: registered new interface driver r8188eu
[ 1.392302] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.398571] nand: Micron MT29F2G08ABAEAWP
[ 1.402598] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.410135] nand: WARNING: pl353-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[ 1.421601] Bad block table found at page 131008, version 0x01
[ 1.427816] Bad block table found at page 130944, version 0x01
[ 1.433905] 10 ofpart partitions found on MTD device pl353-nand
[ 1.439805] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[ 1.446188] Creating 10 MTD partitions on "pl353-nand":
[ 1.451441] 0x000000000000-0x000000780000 : "fsbl"
[ 1.457148] 0x000000780000-0x000000b80000 : "kerneldata"
[ 1.463308] 0x000000b80000-0x000000c00000 : "device-tree"
[ 1.469463] 0x000000c00000-0x000001100000 : "Manufacturedata"
[ 1.475978] 0x000001100000-0x000001600000 : "reserved1"
[ 1.482017] 0x000001600000-0x000002a00000 : "rootfs"
[ 1.487783] 0x000002a00000-0x000003400000 : "firmdata0"
[ 1.493824] 0x000003400000-0x00000a200000 : "siglent"
[ 1.499858] 0x00000a200000-0x00000fc00000 : "datafs"
[ 1.505738] 0x00000fc00000-0x000010000000 : "reserved2"
[ 1.513688] TCP: cubic registered
[ 1.516926] NET: Registered protocol family 17
[ 1.521388] lib80211: common routines for IEEE802.11 drivers
[ 1.527308] Registering SWP/SWPB emulation handler
[ 1.533808] rtc-ds1307 0-0068: setting system clock to 2020-06-02 08:18:52 UTC (1591085932)
[ 1.546668] cramfs_fill_nand blocks is 160-----------------------
[ 1.546668]
[ 1.546668]
[ 1.546668]
[ 1.559627] VFS: Mounted root (cramfs filesystem) readonly on device 31:5.
[ 1.566468] devtmpfs: mounted
[ 1.569783] Freeing unused kernel memory: 200K (40652000 - 40684000)
[ 1.599337] usb 1-1: New USB device found, idVendor=0424, idProduct=2514
[ 1.605968] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.613884] hub 1-1:1.0: USB hub found
[ 1.617718] hub 1-1:1.0: 2 ports detected
Starting rcS...
Mounting filesystem
[ 1.948456] UBI-0: ubi_attach_mtd_dev:attaching mtd8 to ubi0
[ 2.291832] UBI-0: scan_all:scanning is finished
[ 2.303543] UBI-0: ubi_attach_mtd_dev:attached mtd8 (name "datafs", size 90 MiB)
[ 2.310901] UBI-0: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 2.319461] UBI-0: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 2.327952] UBI-0: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 2.336646] UBI-0: ubi_attach_mtd_dev:good PEBs: 720, bad PEBs: 0, corrupted PEBs: 0
[ 2.344380] UBI-0: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 2.353310] UBI-0: ubi_attach_mtd_dev:max/mean erase counter: 7/2, WL threshold: 4096, image sequence number: 1124879481
[ 2.364161] UBI-0: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 720, PEBs reserved for bad PEB handling: 40
[ 2.375111] UBI-0: ubi_thread:background thread "ubi_bgt0d" started, PID 665
[ 2.379086] UBI-1: ubi_attach_mtd_dev:attaching mtd7 to ubi1
[ 2.794881] UBI-1: scan_all:scanning is finished
[ 2.806840] UBI-1: ubi_attach_mtd_dev:attached mtd7 (name "siglent", size 110 MiB)
[ 2.814348] UBI-1: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 2.822932] UBI-1: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 2.831437] UBI-1: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 2.840122] UBI-1: ubi_attach_mtd_dev:good PEBs: 880, bad PEBs: 0, corrupted PEBs: 0
[ 2.847832] UBI-1: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 2.856784] UBI-1: ubi_attach_mtd_dev:max/mean erase counter: 5/1, WL threshold: 4096, image sequence number: 1618119446
[ 2.867633] UBI-1: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 880, PEBs reserved for bad PEB handling: 40
[ 2.878582] UBI-1: ubi_thread:background thread "ubi_bgt1d" started, PID 669
[ 2.888773] UBI-2: ubi_attach_mtd_dev:attaching mtd6 to ubi2
[ 2.931980] UBI-2: scan_all:scanning is finished
[ 2.942379] UBI-2 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[ 2.953344] UBI-2: ubi_attach_mtd_dev:attached mtd6 (name "firmdata0", size 10 MiB)
[ 2.960953] UBI-2: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 2.969522] UBI-2: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 2.978014] UBI-2: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 2.986715] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 2.994347] UBI-2: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 3.003310] UBI-2: ubi_attach_mtd_dev:max/mean erase counter: 3/1, WL threshold: 4096, image sequence number: 1498106769
[ 3.014156] UBI-2: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[ 3.024976] UBI-2: ubi_thread:background thread "ubi_bgt2d" started, PID 673
[ 3.106569] UBIFS: mounted UBI device 1, volume 0, name "siglent", R/O mode
[ 3.113469] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 3.122575] UBIFS: FS size: 104755200 bytes (99 MiB, 825 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[ 3.132292] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 3.137322] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 08B2ABD4-1A1E-4DF4-9158-DC2A5EC267D7, small LPT model
[ 3.200687] UBIFS: mounted UBI device 2, volume 0, name "firm0", R/O mode
[ 3.207393] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 3.216534] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[ 3.225893] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 3.230929] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 404D2EC9-F719-4064-9936-52B4861B89F6, small LPT model
[ 3.244652] UBIFS: background thread "ubifs_bgt0_0" started, PID 678
[ 3.274545] UBIFS: recovery needed
[ 3.352146] UBIFS: recovery completed
[ 3.355797] UBIFS: mounted UBI device 0, volume 0, name "datafs"
[ 3.361738] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 3.370842] UBIFS: FS size: 84439040 bytes (80 MiB, 665 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[ 3.380471] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 3.385501] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 927FB5FE-9078-46E4-8BB5-01A513E5E925, small LPT model
Upgrade start
Configure eth0
Starting mdev
udhcpc (v1.20.1) started
Sending discover...
[ 4.214498] xilinx-dma 40400000.dma: Probing xilinx axi dma engine...Successful
[ 4.239650] xilinx-vdma 43010000.dma: Xilinx AXI VDMA Engine Driver Probed!!
[ 4.253215] sigdma_init++++++
[ 4.279109] siglentkb probe
[ 4.281898] ##### siglentkb registers 5fa9e580 5faba5a4 5fabc5b8
[ 4.303161] usbcore: registered new interface driver mt7601u
[ 4.314912] irq = 169
[ 4.337361] sigirq_init++++++
[ 4.340693] sigirq_cpld++
[ 4.343255] irq = 172
[ 4.345785] sigirq_cpld--
config read
###### Config vdma for wave transform #######
config write
config read
dump s2mm registers
dump mm2s registers
####### done! ########
Config vnc data to memory
Config done!
/lib:/usr/lib:/usr/bin/siglent/lib/qt/lib:/usr/bin/siglent/lib
[ 4.677395] UBIFS: background thread "ubifs_bgt1_0" started, PID 799
ln: /usr/bin/siglent/config/www/web_img/usr: File exists
Starting Lighttpd Web Server: Initializing framebuffer device /dev/fb0...
xres=1024, yres=600, xres[ 4.738195] input: PolyVision Touch Screen as /devices/virtual/input/input1
v=1024, yresv=600, xoffs=0, yoffs=0, bpp=16
Initializing touch device /dev/input/event0 ...
Reading From :(goodix-ts)
buttonMask: xmin:0
xmax: 1024
ymin:0
ymax: 600
Initializing VNC server:
width: 1024
height: 600
bpp: 16
port: 5900
Initializing server...
02/06/2020 08:18:55 Listening for VNC connections on TCP port 5900
[ 4.785407] random: lighttpd urandom read with 17 bits of entropy available
lighttpd.
[ 4.914355] UBIFS: background thread "ubifs_bgt1_0" stops
rcS Complete
/ # Sending discover...
[INFO]:calibrate_t():line=81:calibrate_t::calibrate_t()
[ 8.852781] random: nonblocking pool is initialized
ACQ1 done_value++
Sending discover...
ACQ2 done_value++
MSO done_value++
product_type SDS2004X_PLUS
[INFO]:qui_main():line=183: ms = 12544
mkdir: can't create directory '/usr/bin/siglent/usr/wifi/': File exists
rm: can't remove '/usr/bin/siglent/usr/wifi/wpa_supplicant': No such file or directory
-------------------------OCL init failed.-------------
No lease, failing
[ 12.925507] <<-GTP-INFO->> System resume.
[ 12.925519] gpio-926 (GTP INT IRQ): _gpiod_direction_output_raw: tried to set a GPIO tied to an IRQ as output
[ 12.938943] <<-GTP-INFO->> GTP wakeup sleep.
[ 12.938951] gpio-926 (GTP INT IRQ): _gpiod_direction_output_raw: tried to set a GPIO tied to an IRQ as output
[ 12.978754] <<-GTP-INFO->> Error occured in init_panel, no config sent
rotationAngle: 0 invertx: false inverty: false
Fontconfig warning: line 142: blank doesn't take any effect anymore. please remove it from your fonts.conf
rotationAngle: 0 invertx: false inverty: false
@@@ board_init @@@
[INFO]:GetMcuId():line=891: CMcuSpj::GetMcuId ret =-1
Scope ID: 00 00 00 00 00 00 00 00 00 00 00 00
8dd6-bb73-29a7
ScopeID(64): 4914a72973bbd68d
[INFO]:qui_main():line=206:@ QuiParaFanCtrl = 0
sh: write error: Invalid argument
[ 18.423355] cpldirq_open++
[ 18.428713] cpldirq_open--
drv_instance_manage_t: produce_id: 16001
(DRV_PRODUCT_SDS2000XPLUS_SDG)
_drv_product=5
sh: can't create /mnt/ota/bug.txt: nonexistent directory
[ 18.961189] export_store: invalid GPIO 115
sh: write error: Invalid argument
sh: can't create /sys/class/gpio/gpio115/direction: nonexistent directory
sh: can't create /sys/class/gpio/gpio115/value: nonexistent directory
+++++++++++++++++++++++ load_cali_data ++++++++++++++++++++++++
[INFO]:load_cali_data():line=1561:sds2000xplus_awg OK!!!!!!!!!!!!!!
[INFO]:initialize():line=1474:cali_data_sds2000xplus_awg_t::initialize()--------
Fontconfig warning: line 142: blank doesn't take any effect anymore. please remove it from your fonts.conf
T1 CH3_SKEW = 62.000000 ns
/usr/bin/siglent/usr/usr/Ref_fileA.ref not exist
/usr/bin/siglent/usr/usr/Ref_fileA.ref not exist
T2 CH3_SKEW = 62.000000 ns
$Task start:: awg_thread
$Task start:: usbtmc_interrupt_thread
color_setup == null
Unknown property hight
Unknown property hight
Decode UART: rx read data invalid.
Decode UART: rx read data invalid.
Decode UART: rx read data invalid.
Decode UART: rx read data invalid.
Decode UART: rx read data invalid.
Decode UART: rx read data invalid.
Decode UART: rx read data invalid.
Decode UART: rx read data invalid.
Decode UART: rx read data invalid.
[INFO]:qui_main():line=220:@ ms = 30755
/usr/bin/siglent/usr/usr/Ref_fileA.ref not exist
usbtmc_para = insmod /usr/bin/siglent/drivers/g_usbtmc.ko idVendor=0xf4ec idProduct=0x1011 iManufacturer=Siglent iProduct=SDS2354XPlus iSerialNum=SDS2PCBC4R0071
[ 35.395239] ######################### usb_gadget_probe_driver 3f05b46c ##################
[ 35.403419] usbtmc_bind+++
[ 35.408292] SIGLENT_DEV: SIGLENT_DEV, version: 2007 OCT 06
[ 35.414864] usbtmc_open()++
[ 35.417611] dev->usbtmc_cdev_open ret = 0
[ 35.421636] ret = 0
[ 35.423659] usbtmc_open--
[ 35.426397] show_send_buffer_size = 61440
/usr/bin/siglent/usr/usr/Ref_fileA.ref not exist
/usr/bin/siglent/usr/usr/Ref_fileA.ref not exist
/usr/bin/siglent/usr/usr/Ref_fileA.ref not exist
/usr/bin/siglent/usr/usr/Ref_fileA.ref not exist
/usr/bin/siglent/usr/usr/Ref_fileA.ref not exist
/usr/bin/siglent/usr/usr/Ref_fileA.ref not exist
-
Kengen link
https://repl.it/repls/DirectProbableTwintext (https://repl.it/repls/DirectProbableTwintext)
Both that link and this link produce the same result
https://repl.it/repls/ElasticEnormousMice
I'm putting in the ScopeID(64) from the boot log and trying the generated code for option 4BW05 but no joy.
Any ideas?
-
Kengen link
https://repl.it/repls/DirectProbableTwintext (https://repl.it/repls/DirectProbableTwintext)
Both that link and this link produce the same result
https://repl.it/repls/ElasticEnormousMice
I'm putting in the ScopeID(64) from the boot log and trying the generated code for option 4BW05 but no joy.
Any ideas?
The ScopeID called for is a hexadecimal string retrievable from the scope with an unpublished SCPI command.
Not hard, you'll work it out.
-
Kengen link
https://repl.it/repls/DirectProbableTwintext (https://repl.it/repls/DirectProbableTwintext)
Both that link and this link produce the same result
https://repl.it/repls/ElasticEnormousMice
I'm putting in the ScopeID(64) from the boot log and trying the generated code for option 4BW05 but no joy.
Any ideas?
The ScopeID called for is a hexadecimal string retrievable from the scope with an unpublished SCPI command.
Not hard, you'll work it out.
I have the boot serial output that spits out a 16 digit hex number, is that not it?
The code in the script shows 16 digits too.
Scope ID: 00 00 00 00 00 00 00 00 00 00 00 00
8dd6-bb73-29a7
ScopeID(64): 4914a72973bbd68d
-
Press the Utility Key then -> System Setting -> System Status and all the info is there, then just insert into the fields as needed, lower case as shown in the display
Also all keys should be entered in upper case format for all of them
-
The 16 digit string.
There has been some discussion the 500 MHz option does not work for all but now there are a few scripts available so some might work better than others.....dunno.
@ Dave
PM sent.
-
Kengen link
https://repl.it/repls/DirectProbableTwintext (https://repl.it/repls/DirectProbableTwintext)
Both that link and this link produce the same result
https://repl.it/repls/ElasticEnormousMice
I'm putting in the ScopeID(64) from the boot log and trying the generated code for option 4BW05 but no joy.
Any ideas?
Yeah just someone was being silly with semantics, technically they did have the more 'correct' version
The option code for 500 Mhz is "500M"
-
The 16 digit string.
There has been some discussion the 500 MHz option does not work for all but now there are a few scripts available so some might work better than others.....dunno.
@ Dave
PM sent.
No internal scripts needed.. by anyone, other than the one external python one
-
Press the Utility Key then -> System Setting -> System Status and all the info is there, then just insert into the fields as needed
Also all should be entered in upper case format for all of them
Ah, that's very different to the 16digit ScopeID I got in the boot dump. Still doesn't work unfortunately.
-
The 16 digit string.
There has been some discussion the 500 MHz option does not work for all but now there are a few scripts available so some might work better than others.....dunno.
@ Dave
PM sent.
No internal scripts needed.. by anyone, other than the one external python one
There's more than just one out there ! ;)
-
The option code for 500 Mhz is "500M"
Yes, that's the one I've been using.
-
Press the Utility Key then -> System Setting -> System Status and all the info is there, then just insert into the fields as needed
Also all should be entered in upper case format for all of them
Ah, that's very different to the 16digit ScopeID I got in the boot dump. Will try.
Be sure to use lower case for the scope id too and uppercase for all keys and if it doesnt work im tired and the scope id is upper case :P
Tau: Not my problem if someone gets lost in the maze :P~
-
The bandwidth one might be only doable via the scpi command MCBD <key>
-
Well stupid me can't read my own hand writing. Code now works and was accepted as a valid license but when I repowered (because it didn't actually increase the bandwidth just after entering) the Bandwidth option is now missing completely from the Options menu!
But it still doesn't work!
Strange thing is, my 350MHz labeled model only has 100MHz -3dB bandwidth, tested and confirmed against my Keysight 500MHz.
Something very strange is happening...
BTW, no need for all upper case as someone mentioned.
-
The bandwidth one might be only doable via the scpi command MCBD <key>
Then why did it have the option enter a license code for the BW05 option?
-
Because I'm tired and its fuzzy if both worked
I know it has a bandwidth selector from I think it was 20M 200M and full bw
But that doesn't fit 100M?
Yeah it removes it and your scope badge should have changed to SDS2504X+ on the info page
-
some screens
-
Yeah it removes it and your scope badge should have changed to SDS2504X+ on the info page
Yep, it changed that, I now have a 2504X+, but the bandwidth is still -3dB down at 100MHz on Full BW setting!
-
I now have a 2504X+, but the bandwidth is still -3dB down at 100MHz on Full BW setting!
Interesting, it should be only +0.8dB @ 100 MHz according to the 50 Ohm BW flatness spec in the datasheet. :-//
Nice flat signal source ? Have you confirmed that with a 2nd source ?
-
I now have a 2504X+, but the bandwidth is still -3dB down at 100MHz on Full BW setting!
Interesting, it should be only +0.8dB @ 100 MHz according to the 50 Ohm BW flatness spec in the datasheet. :-//
Nice flat signal source ? Have you confirmed that with a 2nd source ?
Turns out it was the 10bit mode that activated. Turn it back to 8bit and I get 590MHz -3dB bandwidth.
Sure enough, the manual tells you that. Interesting.
-
I now have a 2504X+, but the bandwidth is still -3dB down at 100MHz on Full BW setting!
Interesting, it should be only +0.8dB @ 100 MHz according to the 50 Ohm BW flatness spec in the datasheet. :-//
Nice flat signal source ? Have you confirmed that with a 2nd source ?
Turns out it was the 10bit mode that activated. Turn it back to 8bit and I get 590MHz -3dB bandwidth.
Nice, and it also aligns very well with the graph on P4 of the datasheet where the front end is swept out to 800 MHz.
Sure enough, the manual tells you that. Interesting.
Yes the 10 bit mode BW is clearly specified as typically 100 MHz in the datasheet too on P3.
-
Press the Utility Key then -> System Setting -> System Status and all the info is there, then just insert into the fields as needed
Also all should be entered in upper case format for all of them
Ah, that's very different to the 16digit ScopeID I got in the boot dump. Still doesn't work unfortunately.
The ScopeID for 2000X+ must be extracted with the SCPI command or looked up on the screen.
The ScopeID seen on the boot log was discarded by Siglent and, although it has been present in many models, only SDS5000X uses it. BTW, it's a "hash" of the MCU_ID.
-
https://www.youtube.com/watch?v=HxzQS-Bn2R0 (https://www.youtube.com/watch?v=HxzQS-Bn2R0)
-
I'll open my 100Mhz base model and take pics of the front end you can use
-
The base model is the same front end with the main board also with matching version codes / population
I did try to get to the other side as well but that proved to be a real pain in the ass so i changed my mind lol
-
Wasn´t a surprise for me as I got the 500Mhz hack on my sds2104X+...
-
They know they will sell a lot more 2104X Plus than 2204XPlus and nobody will buy a 2304X,its almost the same price than the SDS5034X.
Its simpler to have only one hardware.
-
Hi,
Mine (a 2104x-plus) stay as SDS2354X-plus (350MHz) when using 500M option key.
I tried again, but same... :-\
Frex
-
Hi,
Mine (a 2104x-plus) stay as SDS2354X-plus (350MHz) when using 500M option key.
I tried again, but same... :-\
Frex
You might want to open it up and see if the board is the same rev / same population of parts.. been some debate about these odd cases
-
Hi,
Mine (a 2104x-plus) stay as SDS2354X-plus (350MHz) when using 500M option key.
I tried again, but same... :-\
Frex
Same here
-
Hi,
Mine (a 2104x-plus) stay as SDS2354X-plus (350MHz) when using 500M option key.
I tried again, but same... :-\
Frex
Only what the annotation in the system info box concerns.
-
Only what the annotation in the system info box concerns.
I will solve that question next so that you can all get some sleep! :)
-
;D :-+
-
I was curious about the keygen in the first post and try it out just for fun ( my scope was unlocked "long" before), Input the scop id and press "Run".
And...
The keys are indentical to mine, nice thing.
May be nothing special to notice for others, but for me who didn´t have any knowledge in the programming/hacking things, it´s pure magic... ;D 8)
-
It's basically Clarke's 3rd law in motion. :-DD
"Any sufficiently advanced technology is indistinguishable from magic."
-
Hi
Long time reader, first time poster.
I've just received an SDS2104X Plus and done the dance to "upgrade" it to 500MHz (Thanks to those responsible for the method!). I've also entered keys for all remaining functions. This has worked fine except for the option ending _FG. In the key gen there is no reference to FG but there is reference to AWG. It seems no matter which key I try I can't get the _FG function unlocked.
I'm sure it's obvious, but what am I missing ?
Thanks
-
I didn't make it clear, although I did mention it, I have tried the AWG key but it is rejected every time.
-
I've solved my AWG key entering issue. The key was valid, but was being rejected. So for anyone who may be having a similar issue :-
When you first enter the options page the option type is pre-populated with the _FG option.
Entering the key without touching anything else fails.
What I did in the end was open the drop down and re-select the _FG option, then enter the key.
That worked.
So it seems that even though the _FG option was pre-populated it wan't necessarily selected.
-
I've solved my AWG key entering issue. The key was valid, but was being rejected. So for anyone who may be having a similar issue :-
When you first enter the options page the option type is pre-populated with the _FG option.
Entering the key without touching anything else fails.
What I did in the end was open the drop down and re-select the _FG option, then enter the key.
That worked.
So it seems that even though the _FG option was pre-populated it wan't necessarily selected.
Yeah this is a bug, i've seen it before now that you mention it so can confirm it
-
Hmmm…
Can´t remember that I got a problem with it.
-
Hmmm…
Can´t remember that I got a problem with it.
Maybe because of this (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3090708/#msg3090708).
-
I had definitely touched FG a couple of times and Key entry was still failing for me.
-
Does this work for SDS5000X ?
-
Does this work for SDS5000X ?
If modded, but how much beyond model name? tv84 would most likely know
-
Wasn't able to use the 500M option, but oddly all of the other codes worked without issue. suggestions?
-
Wasn't able to use the 500M option, but oddly all of the other codes worked without issue. suggestions?
Fat finger?
You can try the SCPI command MCBD
-
For whatever reason, I had to go 100M-> 200M ->350M ->500M. Enter the bandwidth keys in that order.
-
Does this work for SDS5000X ?
I believe I saw on one of the hack scripts it mentioned that it does.
-
Hello Everybody,
I am a long time reader of this fantastic forum and I became a member since a few days. I'm an electronic engineer living in Italy, I normally use some LeCroy scopes at my job
and I recently purchased a Siglent SDS2104X Plus for my personal use, at my home.
After a few days using the instrument to verify the correct behavior, I'm going to apply the hacking procedure, simply using the key generator.
So, before proceeding in that direction, I'd like to ask to the community a quite simple and obvious (...maybe "stupid"...) question: is there a way to get back to the
original status of the device (the default state, with no option nor upgrade keys entrered), in the unlucky case I would need to send the scope to repair, under warranty?
Does it make any difference, in that sense, upgrading the bandwidth entering the keys on instrument panel or via SCPI MCBD command?
Thanks in advance for any feedback!
Best regards.
Sergio
-
Just got my scope from Saelig. All the options worked great, thank you! Had to do the incremental steps on the bandwidth. For me had to do 200M, 350M and then 500M to get the upgrade to work. All the rest just flat out worked on the first try. Cheers
-
So, before proceeding in that direction, I'd like to ask to the community a quite simple and obvious (...maybe "stupid"...) question: is there a way to get back to the
original status of the device (the default state, with no option nor upgrade keys entrered), in the unlucky case I would need to send the scope to repair, under warranty?
Does it make any difference, in that sense, upgrading the bandwidth entering the keys on instrument panel or via SCPI MCBD command?
I don't see any way to uninstall the options, at least in the user menu. Might be some other way to do it or factory restore the unit?
-
So, before proceeding in that direction, I'd like to ask to the community a quite simple and obvious (...maybe "stupid"...) question: is there a way to get back to the
original status of the device (the default state, with no option nor upgrade keys entrered), in the unlucky case I would need to send the scope to repair, under warranty?
Does it make any difference, in that sense, upgrading the bandwidth entering the keys on instrument panel or via SCPI MCBD command?
I don't see any way to uninstall the options, at least in the user menu. Might be some other way to do it or factory restore the unit?
console access and its possible.. not really one to spill the beans on that as a courtesy to siglent.. enough people start doing that and they may rethink their position of letting us easily hack their equipment
-
So, before proceeding in that direction, I'd like to ask to the community a quite simple and obvious (...maybe "stupid"...) question: is there a way to get back to the original status of the device (the default state, with no option nor upgrade keys entrered), in the unlucky case I would need to send the scope to repair, under warranty?
Does it make any difference, in that sense, upgrading the bandwidth entering the keys on instrument panel or via SCPI MCBD command?
Without console access there is but it's not public domain. ;)
The MCBD lets you enter any BW (up or down). The key panel has limitations.
-
So, before proceeding in that direction, I'd like to ask to the community a quite simple and obvious (...maybe "stupid"...) question: is there a way to get back to the original status of the device (the default state, with no option nor upgrade keys entrered), in the unlucky case I would need to send the scope to repair, under warranty?
I'm hopefully receiving mine in the next week or so as well. So I'd be interested to know this as well, but understand if this is a 'sensitive' subject.
-
I thought the hardware was different on the 300Mhz version. That means 300Mhz and up wont work / work correctly?
-
I thought the hardware was different on the 300Mhz version. That means 300Mhz and up wont work / work correctly?
Only 100, 200, 350 MHz models and the optional 500 MHz upgrade in the SDS2000X Plus series.
However, this is the info you seek:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3087116/#msg3087116 (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3087116/#msg3087116)
-
Hi! I am ordering a SDS2104X Plus and I am relatively basing my decision on the ability to hack it (I only need the AWG option for bode plotting). I have read the threads and also the video, but I still have some questions.
Does the hack involve anything ,besides taking the ScopeID from the main screen, generating the keys and typing them on the device.
Has it worked for everyone who tried it?
Does the keygen still work?
Thank you in advance for the answers! :)
-
Hi,
Checked this at last in june, the generated keys were identical so it should work.
Took the keygen from the first post.
-
The bandwidth one might be only doable via the scpi command MCBD <key>
FWIW, on the 100MHz I had, I did it from the front panel, but had to do it in stages, from 100 to 200 to 350 to 500.
I have a question though. When Ch1+Ch2 are used, the sampling rate drops to 1GSa/s. Of course, things then start to go a bit weird beyond about 420MHz, and we see the expected Fs-f aliasing beyond Fs/2 and the counter, for example, shows a 580MHz signal as being 420MHz. On kosher 350MHz units, upgraded to 500MHz, is this still a thing, or do the 350MHz units have additional ADC hardware to maintain the sample rate at 2GSa/s?
The photos mentioned above seem to concentrate on the analog attenuator side alone and not the ADC.
-
FWIW, on the 100MHz I had, I did it from the front panel, but had to do it in stages, from 100 to 200 to 350 to 500.
I have a question though. When Ch1+Ch2 are used, the sampling rate drops to 1GSa/s. Of course, things then start to go a bit weird beyond about 420MHz, and we see the expected Fs-f aliasing beyond Fs/2 and the counter, for example, shows a 580MHz signal as being 420MHz. On kosher 350MHz units, upgraded to 500MHz, is this still a thing, or do the 350MHz units have additional ADC hardware to maintain the sample rate at 2GSa/s?
In a 500 unit, you can only use Ch1+Ch2 up to 350. So if things only go weird after 420, it's within spec.
The MCBD command allows from 100 to 500 in one shot-only. So, makes it easy.
-
Hi,
When Ch1+Ch2 are used, the sampling rate drops to 1GSa/s. Of course, things then start to go a bit weird beyond about 420MHz
Therefore siglent claims to use ch1 or 2 and ch3 or 4 - If you got the 500Mhz option, it will be bandwith-limited to 350Mhz because they know the 1GSa/s thing.
[attachimg=1]
-
FWIW, on the 100MHz I had, I did it from the front panel, but had to do it in stages, from 100 to 200 to 350 to 500.
I have a question though. When Ch1+Ch2 are used, the sampling rate drops to 1GSa/s. Of course, things then start to go a bit weird beyond about 420MHz, and we see the expected Fs-f aliasing beyond Fs/2 and the counter, for example, shows a 580MHz signal as being 420MHz. On kosher 350MHz units, upgraded to 500MHz, is this still a thing, or do the 350MHz units have additional ADC hardware to maintain the sample rate at 2GSa/s?
In a 500 unit, you can only use Ch1+Ch2 up to 350. So if things only go weird after 420, it's within spec.
OK, sounds reasonable.
The MCBD command allows from 100 to 500 in one shot-only. So, makes it easy.
Yeah, I tried that, but no cigar. Probably operator error. I telnetted in on port 5024, *IDN? worked, but I couldn't get MCBD xxxxxxxxxxxxxxxx to do anything, no error or action, on any of the keys. As I say, prolly operator error. I gave up and did them all from the front panel, with the help of a USB keyboard.
-
Hi,
When Ch1+Ch2 are used, the sampling rate drops to 1GSa/s. Of course, things then start to go a bit weird beyond about 420MHz
Therefore siglent claims to use ch1 or 2 and ch3 or 4 - If you got the 500Mhz option, it will be bandwith-limited to 350Mhz because they know the 1GSa/s thing.
(Attachment Link)
Yes, that's precisely the behaviour, it appears to be a different low pass filter, I didn't know if it was a hardware limitation on non-350MHz models. I guess I should RTFM!
-
I have a question though. When Ch1+Ch2 are used, the sampling rate drops to 1GSa/s. Of course, things then start to go a bit weird beyond about 420MHz, and we see the expected Fs-f aliasing beyond Fs/2 and the counter, for example, shows a 580MHz signal as being 420MHz. On kosher 350MHz units, upgraded to 500MHz, is this still a thing, or do the 350MHz units have additional ADC hardware to maintain the sample rate at 2GSa/s?
There are 2 ADC's, each 2 GSa/s with 200 Mpts memory support each.
To satisfy Nyquist a channel need be assigned to each ADC for work to 500 MHz.
Therefore these are a 4ch 350 MHz DSO or 2ch 500 MHz DSO.
Further reading here:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg2786298/#msg2786298 (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg2786298/#msg2786298)
-
I have a question though. When Ch1+Ch2 are used, the sampling rate drops to 1GSa/s. Of course, things then start to go a bit weird beyond about 420MHz, and we see the expected Fs-f aliasing beyond Fs/2 and the counter, for example, shows a 580MHz signal as being 420MHz. On kosher 350MHz units, upgraded to 500MHz, is this still a thing, or do the 350MHz units have additional ADC hardware to maintain the sample rate at 2GSa/s?
There are 2 ADC's, each 2 GSa/s with 200 Mpts memory support each.
To satisfy Nyquist a channel need be assigned to each ADC for work to 500 MHz.
Therefore these are a 4ch 350 MHz DSO or 2ch 500 MHz DSO.
Further reading here:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg2786298/#msg2786298 (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg2786298/#msg2786298)
Yes, I was just querying whether there was something special about the 350MHz model which as I understand it is the only model officially upgradeable to 500MHz. I thought that there might be a technical aspect to this also.
-
Hello,
Disclaimer, I'm not a software guru and limited knowledge with these scopes and "hacking" procedures, and have no knowledge with hacking anything.
We've just received the SDS2102X Plus thanks to Rob at Tautech and Saelig. Have an ongoing project for the scope use and was going to wait until attempting to enable the features, fearing I might hose the scope up.
Curiosity got me and I decided to try an unlock an unimportant feature while waiting for some components, figuring I wouldn't hose up the actual scope. So followed the notes on here and got the scope ID (lower case) from the System Status menu, and didn't include the "-" from the ID as it's xxxx-xxxx-xxxx-xxxx. Then entered this ID sans "-" in the on-line Python script which created all the keys for various features. Tried using the key (Upper case) for the CANFD which failed with a code error message, tried the 1553B with same result. So checked the scope ID and reran the Python script, reentered the keys and failed again, then tried the Bandwidth Option which also failed. The scope software was updated earlier to 1.3.5R5 before any hacking attempts.
Not sure what I'm doing wrong, so any help is greatly appreciated!!
BTW so impressed with the SDS2102X Plus, we just ordered the SDG2042X AWG :)
Best,
-
Not sure what I'm doing wrong, so any help is greatly appreciated!!
Here (https://www.eevblog.com/forum/testgear/sds1104x-e-hack-to-200mhz-and-full-options/msg3184742/#msg3184742).
-
Not sure what I'm doing wrong, so any help is greatly appreciated!!
Here (https://www.eevblog.com/forum/testgear/sds1104x-e-hack-to-200mhz-and-full-options/msg3184742/#msg3184742).
Checked the scope ID and SN from the System Status, ran the indicated python script with scope ID and SN and scope model changed to SDS2000X+, entered the keys generated in scope Options and tried a couple Option Types including Bandwidth, they all failed!!
Best,
-
Not sure what I'm doing wrong, so any help is greatly appreciated!!
Here (https://www.eevblog.com/forum/testgear/sds1104x-e-hack-to-200mhz-and-full-options/msg3184742/#msg3184742).
Checked the scope ID and SN from the System Status, ran the indicated python script with scope ID and SN and scope model changed to SDS2000X+, entered the keys generated in scope Options and tried a couple Option Types including Bandwidth, they all failed!!
Best,
Did you use this keygen ?
https://repl.it/repls/DirectProbableTwintext (https://repl.it/repls/DirectProbableTwintext)
Maybe it needs a different hash code for 2 channel models ?
-
Hello,
The keys need to be in lower case, not upper case as they are shown by the generator. Thanks to Tautech for pointing this out!! Now the scope accepts the keys and I've enabled a few functions including extending BW to 200MHz (havent measured tho), tried 500MHz but got a error message.
Unfortunately a drink (Kobucha) was spilled and went inside the scope and into the front panel. I've disassembled and cleaned as best I could but the front panel controls don't work properly, likely due to leakage between controls and knobs from residue. The scope has been disassembled down to main PCB but I can't get the main PCB removed to get to the control panel PCB underneath. It seems the final attachment is around the input connector region (this is a 2 channel scope) and I can't see any screws and seems the attachment is by the input BNC connectors being soldered into place. Hopefully this isn't the case as they look like it would be difficult to unsolder and remove the main PCB.
Anyway, good news is that the keys now work in lower case, bad news is the scope is hosed up by another means :-\
Any help with the main PCB removal to get to the front panel PCB is appreciated.
Best,
Edit: The label around the input BNC connectors covers bolts that hold the cover on. Removing the label and the bolts allows access to the front PCB. After following this the PCB and push-button membrane were cleaned, dried and replaced. Now the scope is fully functional :phew:
-
so..today this is good, very good to have the oportunety to do this.
But on the long run, dont we shoot our self in the foot..
Will the scope manufators make software uppgrading imposibol on new models becouse of this hacking.. They will come up with somthing like verification tru the web or somthing else to make it harder..
just woundering... :o
Got a rigol MSO4025 thats fully hacked so saved a load of money there. 8)
-
Will be happy when you tell me/us, what your post will have to do with the topic here.
Do you own/got a SDS2K+ and hacked it successfully ?
-
Make you happy ?, happy to say that im not gone do that!
-
I'm either VERY STUPID.... Or Siglent has somehow prevented the options "modifications" on the 1.3.5R10 firmwares.
Pretty sure it's one of those two.
I was able to get the 500Mhz bandwidth option working using SCPI command for bandwidth. No issue. So looking at Python code, I have the right SCOPEID and MODEL and HASHKEY, but the options are SERIAL and MODEL.
I've tried: every generator, every upper and lower key on the front end and via SCPI using LCSLI OPTION,key (including option,key and OPTION,KEY and spaces vs comas), I've 10x confirmed my serial number on the back of the device on the and sys info and via SCPI, serial and lower, I took the one 0 and made it an O, reboots.
I can find no indication of anything I've missed. I have 28-30 "Remaining" on all options. Oddly, I have no front end option for Logic Analyzer at all, I'll ignore that for now.
Anything I might be missing!?
EDIT: MOSTLY SOLVED.
Key take aways...
* There are at least 5 different keygens and 3 of them DO NOT WORK for the SDS2000X+. You want the one with "'AWG', 'WIFI', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA'" options. Not the ones with PA, 16LA, etc. Notice these keygens do NOT use the SERIAL at all.
* I could not get any keys to work on the 2000X+ using SCPI, all worked with front end using lowercase.
* I did "AWG" (frequency generator, previously FG) last, and this was a problem. When you go into the options screen it shows FG in the drop down, but it's not really selected. If you save AWG/FG for last, you may be stuck with no way to drop that down to select it, and no way to hit the install key. WORKAROUND: Hook up a keyboard, type the key in, and hit ENTER, TAB, ENTER, TAB, over and over. It worked after about 6 times or so for me. You might clear your key and need to enter it again, IDK, worked for me.
* For being a meticulous bunch of engineering types you guys REALLY SUCK at versioning and comments in your keygen code. Seriously. Put a comment in with at least what model you think this works for.
-
But on the long run, dont we shoot our self in the foot..
Will the scope manufators make software uppgrading imposibol on new models becouse of this hacking.. They will come up with somthing like verification tru the web or somthing else to make it harder..
just woundering... :o
Got a rigol MSO4025 thats fully hacked so saved a load of money there. 8)
So spend the $ you saved on more equipment, that will keep the manufactures happy ;D
Best,
-
Can anyone confirm the LOGIC ANALYZER SPL16 hardware needs a key on the S2000X+?
According to the links for siglent-spl2016-plus-16-channel-logic-probe-module-with-license-key it does, but I can see no option for it, and of the keygens (that work) there seems to be no license option. For the keygens that DO NOT work, there is a LA16.
I haven't had a second to hook it up, so I assume when I do it's just going to work. But it's a little wierd they want to sell you a software license when there is no where to enter it... No?
-
Can anyone confirm the LOGIC ANALYZER SPL16 hardware needs a key on the S2000X+?
According to the links for siglent-spl2016-plus-16-channel-logic-probe-module-with-license-key it does, but I can see no option for it, and of the keygens (that work) there seems to be no license option. For the keygens that DO NOT work, there is a LA16.
I haven't had a second to hook it up, so I assume when I do it's just going to work. But it's a little wierd they want to sell you a software license when there is no where to enter it... No?
Option page:
https://siglentna.com/product/16-digital-channelssoftware/
-
Can anyone confirm the LOGIC ANALYZER SPL16 hardware needs a key on the S2000X+?
According to the links for siglent-spl2016-plus-16-channel-logic-probe-module-with-license-key it does, but I can see no option for it, and of the keygens (that work) there seems to be no license option. For the keygens that DO NOT work, there is a LA16.
I haven't had a second to hook it up, so I assume when I do it's just going to work. But it's a little wierd they want to sell you a software license when there is no where to enter it... No?
Yes, there is a software key to purchase on top of the hardware itself. That software key can be hacked.
-
Can anyone confirm the LOGIC ANALYZER SPL16 hardware needs a key on the S2000X+?
According to the links for siglent-spl2016-plus-16-channel-logic-probe-module-with-license-key it does, but I can see no option for it, and of the keygens (that work) there seems to be no license option. For the keygens that DO NOT work, there is a LA16.
I haven't had a second to hook it up, so I assume when I do it's just going to work. But it's a little wierd they want to sell you a software license when there is no where to enter it... No?
Option page:
https://siglentna.com/product/16-digital-channelssoftware/
Yea. Saw that... BUT... I have no 16LA or LogicAnalyzer or etc in my options page. And the keygens with 16LA that base off the serial number DO NOT seem to work at all. I could change the code that does work (the one that uses device code + model for bandwidth and options) but I've also had no luck with SCPI commands.
If it wasn't working would it allow digital as a "channel"? Because it currently does.
-
Hi,
I have no 16LA or LogicAnalyzer or etc in my options page
But you got the MSO (Mixed Signal Oscilloscope) option, that´s it.
-
OOOOOOOOOOooohhhhh..... I'm dumb.
Thanks guys.
-
Is there nobody who could assist to my question: a connector diagram resp. a layout of the ( PCI? ) plug. I wouldn't need a sophisticated probe as I'm analyzing only slow logic.
Would there be a need for protection circuits ?
Thanks in advance,
Regards
Tom
-
Hey I want this scope.
I wanna upgrade from a sds2352X-E t another "350 MHz upgrade".
Is it all fine and dandy?
1399$ + the LA hardware only and I'm good to go beat some MSO5074 boys???
-
Hi,
Apart from the fact that this is not the topic for that question here(have a look at my threadlist in the signature):
"To beat some MSO5074 boys" shouldn´t be an argument for buying the siglent... ;)
-
Seems to me by the title that this is relevant for me.
Can you confirm or deny your positive experience?
Me and Siglent will smooth things if ever... :-DD
I'm good to go beat some MSO5074 boys at their own game ?
-
:palm:
-
:palm:
-
:palm:
-
Is there nobody who could assist to my question: a connector diagram resp. a layout of the ( PCI? ) plug. I wouldn't need a sophisticated probe as I'm analyzing only slow logic.
Would there be a need for protection circuits ?
Thanks in advance,
Regards
Tom
-
:palm:
-
Is there nobody who could assist to my question: a connector diagram resp. a layout of the ( PCI? ) plug. I wouldn't need a sophisticated probe as I'm analyzing only slow logic.
Would there be a need for protection circuits ?
Thanks in advance,
Regards
Tom
Wrong thread.
Start reading for a few pages from here Tom:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3020534/#msg3020534 (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3020534/#msg3020534)
-
For the record: the SDS5000X seems to use always the scope ID and never the serial number. Option string is "SENT" for SENT (not so surprising) and "PWA" for PA. No idea about Manchester ("Manch") though. There doesn't seem to be a way to enter the code anyway.
-
I recently bought 2 units for the lab.I could find some time last Friday to hack them.
it worked well for the 1st unit. I also unlock the second one. Things happened to work flawlessly too but right after the process, the scope simply turned off and never turned on again.
Did anybody face such an issue ?
-
I recently bought 2 units for the lab.I could find some time last Friday to hack them.
it worked well for the 1st unit. I also unlock the second one. Things happened to work flawlessly too but right after the process, the scope simply turned off and never turned on again.
Did anybody face such an issue ?
might be just a doa unit.. if you didnt do anything internally with the OS and was just keys through the UI that wouldnt have caused that
hard call to say if you should even open it up and try the uart port.. if it seems completely dead you are probly better off getting an exchange
-
I recently bought 2 units for the lab.I could find some time last Friday to hack them.
it worked well for the 1st unit. I also unlock the second one. Things happened to work flawlessly too but right after the process, the scope simply turned off and never turned on again.
:wtf:
Did anybody face such an issue ?
Never, not with 100's of Siglent units.
Check the silly stuff first like mains cable and rear mains fuse before filing a warranty claim with your supplier.
-
I did exchange my mains cables. I did check the power socket too... no green light.
Good thing is that 1 of the 2 is working.
-
Good thing is that 1 of the 2 is working.
LOL :-DD
I think, the second unit was made on monday* , the hack won´t done the harm to it.
*) German speech for a unit which is going faulty very early
-
I just wonder: there still seems to be the FW bug that you can't enter the key for the last option in the list (which should be "Manch" now) if all the other options are enabled. Or to be more exact: you can't select the option type as the combobox is grayed out and stuck to "FG".
Somewhere someone talked about a workaround about hitting Tab several times on an USB keyboard but that didn't work for me or I didn't get the idea correctly.
Also the LCISL SCPI command doesn't seem to work (responds with OK whatever you send there, but the option is not enabled).
Is there any working way to enable the last option?
-
with me there is the possibility to enter "SENT and MANCH" with key.
Unfortunately the keygens do not work for me anymore
https://repl.it/@wxq849034624/PrettyAbleGuiltware-1#main.py
i have saved my old keys these still work, the script returns completely different keys
edit:
i tried something else, added the phy-code in the appendix (thanks to the creator), here -> https://repl.it/languages/python3, ScopeID is clear and the created keys were correct again.
So I could activate the new options.
-
The problem is explained here:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3323244/#msg3323244 (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3323244/#msg3323244)
I've never run any python scripts locally and I've now embarked upon a search for tutorials on the subject.
John
-
The problem is explained here:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3323244/#msg3323244 (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3323244/#msg3323244)
John
I did not see that, of course that explains everything...
-
I'm hoping someone will help an old Aspie with what is probably an over literal interpretation of what is required for using the python script.
Pretty please?
Am I correct in understanding that upon turning on the scope:
1) I get my Scope ID from Utility -> System Setting -> System Status
2) I use those 16 characters, sans '-' dashes, using only lower case, and enter them into the python hashing script - replacing the value of the SCOPEID variable
3) I do /NOT/ put in my /ACTUAL/ model (SDS2104X+) but instead use the base model id of 'SDS2000X+' in the appropriate variable again in the python script
4) On the scope, under Utility -> Options I select the option 'SDS_2000XP_4BW02' and enter - first - the key value for 100M, all in lower case, then hit 'Install'?
I ask because I get an error dialog saying 'Invalid Data' every time.
My data is as follows, with the last four digits obfuscated for obvious reasons.
scope_id = "0040-001b-3da1-...."
serial_no = "SDS2PCBQ4R...."
model_no = "SDS2104X+"
software_version = "1.3.5R7"
uboot_versio = "5.0"
fpga_version = "2020-04-26"
cpld_version = "03"
hardware_version = "02-00"
Thank you to anyone willing to read this for your time, my apologies but I have read through the different threads in what I believe is a careful manner but I'm clearly being an idiot.
-
I'm hoping someone will help an old Aspie with what is probably an over literal interpretation of what is required for using the python script.
Pretty please?
Am I correct in understanding that upon turning on the scope:
1) I get my Scope ID from Utility -> System Setting -> System Status
2) I use those 16 characters, sans '-' dashes, using only lower case, and enter them into the python hashing script - replacing the value of the SCOPEID variable
3) I do /NOT/ put in my /ACTUAL/ model (SDS2104X+) but instead use the base model id of 'SDS2000X+' in the appropriate variable again in the python script
4) On the scope, under Utility -> Options I select the option 'SDS_2000XP_4BW02' and enter - first - the key value for 100M, all in lower case, then hit 'Install'?
I ask because I get an error dialog saying 'Invalid Data' every time.
My data is as follows, with the last four digits obfuscated for obvious reasons.
scope_id = "0040-001b-3da1-...."
serial_no = "SDS2PCBQ4R...."
model_no = "SDS2104X+"
software_version = "1.3.5R7"
uboot_versio = "5.0"
fpga_version = "2020-04-26"
cpld_version = "03"
hardware_version = "02-00"
Thank you to anyone willing to read this for your time, my apologies but I have read through the different threads in what I believe is a careful manner but I'm clearly being an idiot.
That's pretty well correct. The only thing you need to edit in that script is the scope-id exactly as you described. Unfortunately, that script has been set to read only so any edits are simply ignored when you hit the run button. The only way now is to copy the content of that script file to another locally stored empty *.py file on your system and run it from a locally installed python interpreter. I'm not sure whether the imported hashlib on line 1 is a special library or just a standard one included with all recent versions of the Python interpreter.
I'm running Linux Mint 17.1 and, in common with most Linux distros, Python is one of the many programming packages pre-installed on the system. Unfortunately for me, I've never knowingly run any python scripts (perl, yes since I use get_iplayer) so I landed up floundering around, trying to get my copy of that script to run. I even thought to redirect any output to a text file but it remained stubbornly empty after it ran with a ton of errors displayed on the console. TBH, it was late in my day (4:30 am!) so I wasn't too surprised with only an hour's worth of 'learning python' under my belt. ;)
BTW, you might want to switch the digits 5 and 7 round in the software version you just posted. :)
John
-
I'm hoping someone will help an old Aspie with what is probably an over literal interpretation of what is required for using the python script.
Pretty please?
Am I correct in understanding that upon turning on the scope:
1) I get my Scope ID from Utility -> System Setting -> System Status
2) I use those 16 characters, sans '-' dashes, using only lower case, and enter them into the python hashing script - replacing the value of the SCOPEID variable
3) I do /NOT/ put in my /ACTUAL/ model (SDS2104X+) but instead use the base model id of 'SDS2000X+' in the appropriate variable again in the python script
4) On the scope, under Utility -> Options I select the option 'SDS_2000XP_4BW02' and enter - first - the key value for 100M, all in lower case, then hit 'Install'?
I ask because I get an error dialog saying 'Invalid Data' every time.
My data is as follows, with the last four digits obfuscated for obvious reasons.
scope_id = "0040-001b-3da1-...."
serial_no = "SDS2PCBQ4R...."
model_no = "SDS2104X+"
software_version = "1.3.5R7"
uboot_versio = "5.0"
fpga_version = "2020-04-26"
cpld_version = "03"
hardware_version = "02-00"
Thank you to anyone willing to read this for your time, my apologies but I have read through the different threads in what I believe is a careful manner but I'm clearly being an idiot.
That's pretty well correct. The only thing you need to edit in that script is the scope-id exactly as you described. Unfortunately, that script has been set to read only so any edits are simply ignored when you hit the run button. The only way now is to copy the content of that script file to another locally stored empty *.py file on your system and run it from a locally installed python interpreter. I'm not sure whether the imported hashlib on line 1 is a special library or just a standard one included with all recent versions of the Python interpreter.
I'm running Linux Mint 17.1 and, in common with most Linux distros, Python is one of the many programming packages pre-installed on the system. Unfortunately for me, I've never knowingly run any python scripts (perl, yes since I use get_iplayer) so I landed up floundering around, trying to get my copy of that script to run. I even thought to redirect any output to a text file but it remained stubbornly empty after it ran with a ton of errors displayed on the console. TBH, it was late in my day (4:30 am!) so I wasn't too surprised with only an hour's worth of 'learning python' under my belt. ;)
BTW, you might want to switch the digits 5 and 7 round in the software version you just posted. :)
John
Thank you SO very much for taking the time to reply John. I'm a software developer actually, so the python is cool for me.
At present, the options menu item 'SDS_2000XP_4BW02' which is last on the list has no value - just 'optional'. Is that what your's had - what you expect me to see before I enter any keys?
I have tried starting with 100M and 200M to no avail. Can you/anyone confirm that I should not be using my 'real' product model with the code, but only 'SDS2000X+' exactly as typed there?
Thank you again so very much indeed!
ed
-
Copy and paste the following code here, you must not be logged in for the page to work
https://repl.it/languages/python3
To find your scope id, use scpi command SCOPEID?
To enter keys, use scpi command LCISL optioncode,hexkey
To change bandwidth, use scpi command MCBD hexkey
-------
import hashlib
SCOPEID = '0000000000000000'
Model = 'SDS2000X+'
bwopt = ('25M', '40M', '50M', '60M', '70M', '100M', '150M', '200M', '250M', '300M', '350M', '500M', '750M', '1000M', 'MAX', 'AWG', 'WIFI', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA', 'MANC', 'SENT')
hashkey = '5zao9lyua01pp7hjzm3orcq90mds63z6zi5kv7vmv3ih981vlwn06txnjdtas3u2wa8msx61i12ueh14t7kqwsfskg032nhyuy1d9vv2wm925rd18kih9xhkyilobbgy'
def gen(x):
h = hashlib.md5((
hashkey +
(Model+'\n').ljust(32, '\x00') +
opt.ljust(5, '\x00') +
2*((SCOPEID + '\n').ljust(32, '\x00')) +
'\x00'*16).encode('ascii')
).digest()
key = ''
for b in h:
if (b <= 0x2F or b > 0x39) and (b <= 0x60 or b > 0x7A):
m = b % 0x24
b = m + (0x57 if m > 9 else 0x30)
if b == 0x30: b = 0x32
if b == 0x31: b = 0x33
if b == 0x6c: b = 0x6d
if b == 0x6f: b = 0x70
key += chr(b)
return key.upper()
for opt in bwopt:
print('{:5} {}'.format(opt, gen(SCOPEID)))
--------
-
@elasia you are amazing, thank you! I think what I was missing is that I was trying to work through the touch screen - I have not yet used scpi. I will do my homework and endeavour to understand that approach and will follow your very kind instructions. Thanks so much!
-
I'm hoping someone will help an old Aspie with what is probably an over literal interpretation of what is required for using the python script.
Pretty please?
Am I correct in understanding that upon turning on the scope:
1) I get my Scope ID from Utility -> System Setting -> System Status
2) I use those 16 characters, sans '-' dashes, using only lower case, and enter them into the python hashing script - replacing the value of the SCOPEID variable
3) I do /NOT/ put in my /ACTUAL/ model (SDS2104X+) but instead use the base model id of 'SDS2000X+' in the appropriate variable again in the python script
4) On the scope, under Utility -> Options I select the option 'SDS_2000XP_4BW02' and enter - first - the key value for 100M, all in lower case, then hit 'Install'?
I ask because I get an error dialog saying 'Invalid Data' every time.
My data is as follows, with the last four digits obfuscated for obvious reasons.
scope_id = "0040-001b-3da1-...."
serial_no = "SDS2PCBQ4R...."
model_no = "SDS2104X+"
software_version = "1.3.5R7"
uboot_versio = "5.0"
fpga_version = "2020-04-26"
cpld_version = "03"
hardware_version = "02-00"
Thank you to anyone willing to read this for your time, my apologies but I have read through the different threads in what I believe is a careful manner but I'm clearly being an idiot.
That's pretty well correct. The only thing you need to edit in that script is the scope-id exactly as you described. Unfortunately, that script has been set to read only so any edits are simply ignored when you hit the run button. The only way now is to copy the content of that script file to another locally stored empty *.py file on your system and run it from a locally installed python interpreter. I'm not sure whether the imported hashlib on line 1 is a special library or just a standard one included with all recent versions of the Python interpreter.
I'm running Linux Mint 17.1 and, in common with most Linux distros, Python is one of the many programming packages pre-installed on the system. Unfortunately for me, I've never knowingly run any python scripts (perl, yes since I use get_iplayer) so I landed up floundering around, trying to get my copy of that script to run. I even thought to redirect any output to a text file but it remained stubbornly empty after it ran with a ton of errors displayed on the console. TBH, it was late in my day (4:30 am!) so I wasn't too surprised with only an hour's worth of 'learning python' under my belt. ;)
BTW, you might want to switch the digits 5 and 7 round in the software version you just posted. :)
John
Thank you SO very much for taking the time to reply John. I'm a software developer actually, so the python is cool for me.
At present, the options menu item 'SDS_2000XP_4BW02' which is last on the list has no value - just 'optional'. Is that what your's had - what you expect me to see before I enter any keys?
I have tried starting with 100M and 200M to no avail. Can you/anyone confirm that I should not be using my 'real' product model with the code, but only 'SDS2000X+' exactly as typed there?
I'm sorry but I also didn't follow your suggestion to swap the 5 and the 7 - the system status screen definitely says 1.3.5R7 but I assume I'm being thick?
Thank you again so very much indeed!
ed
Here's a complete list of all the firmware versions to date. As you can see, ver 1.3.5R7 is not in that list, hence my assumption of a transcription error in your post.
Version Compatibility
Source Version
Object Version
Compatibility
1.3.5R10
1.3.7R5
Tested
1.3.5R5
1.3.7R5
Tested
1.3.5R3
1.3.7R5
Tested
1.3.5R5
1.3.5R10
Tested
1.3.5R3
1.3.5R10
Tested
1.3.5R3
1.3.5R5
Tested
When I applied the keygen hacks the first time round (whilst the script could still be edited and run), that was a month or two back and I wasn't taking notes so my recollection is now a little hazy. However, having worked backwards from the 500MHz option before hitting the, afaicr, 200MHz option which would actually accept a licence key, the next BW option was the 350MHz one which I applied the licence key to, followed finally by the 500MHz option, at which point, the BW option disappears from the list. The current BW state now being identified by the change of model number to SDS2504X plus.
My own options list now includes the two new options, "SENT" and "MANC" listed as Temporary with remaining times set to 30. All the other applied options, except the BW one, are listed as applied with XX in the remaining times column.
The "4BW02" looks like the 200MHz option to me (ISTR having to infer which of the BW options in the generated licence keys list was required for the displayed BW option and apply it to change the displayed BW option to the next higher one and "Rinse and repeat" until no more BW options were displayed after applying the 500MHz licence key.
It looks to me as though it's still waiting to accept a valid license key to upgrade from the existing 100MHz BW to the next available BW option of 200MHz. If you're doing this for the first time with that script, you'll just keep seeing "Invalid Licence key" every time you use the 200MHz licence key on that generated list since it's simply the result of the preset 0000000000000000 value already displayed for the scope-id variable.
The only way round the blockage is to copy and paste the contents of that script file into an empty *.py file stored on a local disk drive which will let you edit the scope-id variable with your actual scope-id. Actually, that's not strictly true. It seems you can get the script to run remotely by signing up (apparently, you can get away with using a fake email address) but if you can run run a correctly edited copy on your own machine, why give them the satisfaction of forcing you to sign up, even if it is with a fake email address? :)
Keep the model number as shown in the script. It's only the scope-id that needs to be entered to generate a set of valid license keys for your scope.
BTW, if you do manage to successfully run that script locally, please let us know. I'd appreciate an "Idiot's Guide" to doing likewise. However, I've already asked this favour from steve1515 in response to his posting here:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3323244/#msg3323244 (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3323244/#msg3323244)
Just let me know first before launching into producing an idiot's guide. :)
[EDIT 2020-11-13 15:38 UTC] Don't bother, Elasia kindly provided the solution. I merely copied and pasted my already prepared local copy of the original script over the hello world example script and copied and pasted the results straight back to my empty report.txt file. I only wanted the last two items and the license keys worked! :)
John
-
@elasia you are amazing, thank you! I think what I was missing is that I was trying to work through the touch screen - I have not yet used scpi. I will do my homework and endeavour to understand that approach and will follow your very kind instructions. Thanks so much!
I've copied and pasted Elasia's excellent post into a text file for future reference.
In my case, when it came to copying and pasting, I used my own already edited copy of the licence hack script and then pasted the results into an empty report.txt file I'd set up to redirect the output of my local python script run which had failed (hence the empty report.txt file so conveniently waiting to accept the results from the remote script run :) ).
You can get the scope-id from the System Setting > System Status screen info - no need to use any SCPI commands. Also, you can just use the on screen licence key entry in the options window in the Utility menu. It's only when you want to revert BW settings or try the oddball ones both below and above the 500MHz limit that don't appear in the on screen licence key entry system that you'll need to use SCPI commands.
Getting this latest license hack script to run using your actual scope-id rather than the pre-loaded 0000000000000000, is the key to success. That and making a full copy of the script's output list of keys for safe keeping.
Thanks to Elasia, it seems I don't need to learn Python after all (at least not yet)! :)
John
-
Thank you again John, Elasia et al for so much kindness!
In scratching my head about that firmware numbering question, I went ahead and installed latest (1.3.7R5 at time of this writing). Lo and behold, now things like the web interface 'magically' became available to me. I should have heeded my own mantra - upgrade to latest before you get cross!
I took the web interface 'Instrument Control' approach for the UI, and upon doing so /carefully/, I found a single digit transposition error in my scope_id - which I imagine did the trick.
Bandwidth in the order of 100M-> 200M ->350M ->500M worked fine, as did the full list of software option keys.
In case it helps you or someone else, here is my final python script https://github.com/ehagerty/sds2000xplus (https://github.com/ehagerty/sds2000xplus). I was not sure if this would constitute a legal liability in making the repo public - if anyone believes so do let me know.
All the best,
Ed
PS - now properly anonymised! :palm:
-
Thank you again John, Elasia et al for so much kindness!
In scratching my head about that firmware numbering question, I went ahead and installed latest (1.3.7R5 at time of this writing). Lo and behold, now things like the web interface 'magically' became available to me. I should have heeded my own mantra - upgrade to latest before you get cross!
I took the web interface 'Instrument Control' approach for the UI, and upon doing so /carefully/, I found a single digit transposition error in my scope_id - which I imagine did the trick.
Bandwidth in the order of 100M-> 200M ->350M ->500M worked fine, as did the full list of software option keys.
In case it helps you or someone else, here is my final python script https://github.com/ehagerty/sds2000xplus (https://github.com/ehagerty/sds2000xplus). I was not sure if this would constitute a legal liability in making the repo public - if anyone believes so do let me know.
All the best,
Ed
I don't know about the legal ramifications but I do hope the scope-id and serial number have been obfuscated. TBH, they look very real to me. I'd obfuscate or otherwise anonymise them quick smart if they are real numbers if I were you. ::)
John
-
Thanks for this. Worked a treat. I started with a 100 Mhz 4 channel & ended with a 500 Mhz 4 channel with AWG & MSO.
-
Thanks for this. Worked a treat. I started with a 100 Mhz 4 channel & ended with a 500 Mhz 4 channel with AWG & MSO.
Plus all the other options I hope !
Yeah you got yours just before the option package was offered for free with any model in the SDS2000X Plus range.
-
Had some free time and decided to try and up the SDS2102X Plus BW to 500MHz, it's previously been "enabled" to 350MHz. Ran the mentioned Python script to create the keys for various functions, which I enabled two that hadn't been enabled, these are SENT and Manch. This went fine from the "Options" menu, but as noted by others there is no BW Option Type shown in the Options table.
Followed the scope Operations Manual to telnet in and checked the ID with SCPI and command SCOPEID? and got the proper returned information. Now I'm stumped on how to enter the exact proper syntax for the SCPI command MCBD with the proper info for enabling the 500MHz BW. Tried MCBD key, MCBD <key>, or MCBD "key", these didn't work, so asking for help with the exact syntax with the SCPI command MCBD to enable the BW to 500MHz from 350MHz.
Best & Thanks in advance,
-
MCBD key (in uppercase)
PS: I hope you are not issuing SCPI commands on a telnet prompt... ::)
-
Tried MCBD KEY in upper case from the SCPI >> prompt (after open IP address 5024 from telnet prompt and getting the Welcome to the SCPI greeting).
I've tried this a couple times, and shut the scope down also. Still no luck, Model: still indicates SDS2353X Plus after rebooting.
Maybe this is one of those that can't be upgraded beyond 350MHz??
Best,
-
Tried MCBD KEY in upper case from the SCPI >> prompt (after open IP address 5024 from telnet prompt and getting the Welcome to the SCPI greeting).
I've tried this a couple times, and shut the scope down also. Still no luck, Model: still indicates SDS2353X Plus after rebooting.
Maybe this is one of those that can't be upgraded beyond 350MHz??
Best,
I forget off the top of my head but there is a reason for it... the 350MHz only ones are a myth, check the main thread for the scope when I opened mine up and tv84 and I went forth hacking it.. reason is buried in there somewhere and how to deal with it
-
Tried MCBD KEY in upper case from the SCPI >> prompt (after open IP address 5024 from telnet prompt and getting the Welcome to the SCPI greeting).
I've tried this a couple times, and shut the scope down also. Still no luck, Model: still indicates SDS2353X Plus after rebooting.
Maybe this is one of those that can't be upgraded beyond 350MHz??
Best,
For the 2ch Plus, SDS2102X+ only the 100 to 350 MHz BW upgrade is officially offered: SDS2000XP-2BW03
Whereas the 4ch models have the full BW upgrade path, 100-200, 200-350, 350-500.
Therefore it may not be possible to bump the 2ch version to 500 MHz, IDK.
https://int.siglent.com/products-ware/sds2000xp/
-
:palm:
Of course your scope still says SDS235X... To change the model, you have to change the .CFG!
One thing is the model reference, the other is the BW. The scope should be at 500 MHz by now.
Arghhh.... You owe me a beer for finding this one again: here (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3088181/#msg3088181)
-
Ok I've done a quick test and the scope BW has been extended to ~615MHz :)
I had thought the name would change as well, I recall it changed when I initially upgraded the scope from the Options section??
Later I'll try and get the proper model name changed by editing the .CFG file as mentioned.
BTW I owe you way more than a brew :-+
Best,
-
Later I'll try and get the proper model name changed by editing the .CFG file as mentioned.
Simply copy the file I attached (the other thread) and overwrite yours. Sync and reboot.
-
Ok, I'm confused or being stupid?
Just taken delivery of an SDS2104X+ direct from Siglent, and a number of the options are showing as permanent, straight out of the box.
FG, FlexRay, CANFD, I2S, 1553B and PA are all showing "Permanent".
I though all these were paid options?
-
It's called "Promotion".
-
It's called "Promotion".
LOL, yes.
It wasn't showing on the web site when I ordered, but now I've gone back there, the promotion is showing, and because the order actually came direct from Siglent, it seems I automatically got the promotion upgrade :-+
Really only need to do the BW upgrade and I'll be very happy.
-
Fully upgraded, and reports as SDS2504X Plus, without having to apply the cfg file change.
Thank you to everyone who helped to support this.
-
It's called "Promotion".
LOL, yes.
It wasn't showing on the web site when I ordered, but now I've gone back there, the promotion is showing, and because the order actually came direct from Siglent, it seems I automatically got the promotion upgrade :-+
Really only need to do the BW upgrade and I'll be very happy.
Decodes Sent and Manchester should also be licensed as permanent as part of the promo. If you haven't got them licensed contact your supplier with your SN# and Scope ID so they can send you the codes to install.
As FW V1.3.7R5 that added Sent and Manchester was only publicly released after the start of the promotion there will be a few units still sold without these enabled.
-
Decodes Sent and Manchester should also be licensed as permanent as part of the promo. If you haven't got then licensed contact your supplier with your SN# and Scope ID so they can send you the codes to install.
As FW V1.3.7R5 that added Sent and Manchester was only publicly released after the start of the promotion there will be a few units still sold without these enabled.
Thank you, I'll get in touch with them :)
-
Just purchased a SDS2104x PLUS , (and it came with SDS2000X Plus Firmware - 1.3.7R5 )
So I copied the python code from https://repl.it/@wxq849034624/PrettyAbleGuiltware-1#main.py (https://repl.it/@wxq849034624/PrettyAbleGuiltware-1#main.py)
and pasted it into https://www.programiz.com/python-programming/online-compiler/ (https://www.programiz.com/python-programming/online-compiler/) (so I could edit the scopeID without having to register on the repl.it site)
Then copied my scopeID from: Utility/System Setting/System status on the scope menu's to the above python code, pressed Run and up popped up all the keys I needed.
The only slight stumbling block was I had to go from my base 100MHz to 200Mhz, then I had to jump to the 350Mhz key, then on to the final destination 500Mhz, because the others inbetween all produced "Invalid data"
The Bandwidth keys needed a re-boot afterwards, the other options (MSO, MANC and SENT) didn't.
Scope now reports on screen as a SDS2504X PLUS , I didn't need to go near a computer connection, all done on the 'scope screen.
Thanks to all concerned. :-+
-
Can you test if the 500MHz is actually working by making some measurements in this range?
-
Can you test if the 500MHz is actually working by making some measurements in this range?
Moi ? ..... Currently not , I've nothing in the workshop with anywhere near , I really only upped it to 500MHZ for the moment because the <free> option was there.
-
Not very scientific I'm afraid, just something quickly put together.
0dBm from TG output on SVA1032X via coax at 100 and 500MHz
-
I am going to buy SDS2104X plus and hack it.
Is there no modification of hardware for hack?
After hack, Can I download firmware of SDS2000X plus? Or do I need to download firmware?
Thanks.
-
I am going to buy SDS2104X plus and hack it.
Is there no modification of hardware for hack?
After hack, Can I download firmware of SDS2000X plus? Or do I need to download firmware?
Thanks.
No hardware mods needed, Follow this that I just did and you'll be fine:
So I copied the python code from https://repl.it/@wxq849034624/PrettyAbleGuiltware-1#main.py (https://repl.it/@wxq849034624/PrettyAbleGuiltware-1#main.py)
and pasted it into https://www.programiz.com/python-programming/online-compiler/ (https://www.programiz.com/python-programming/online-compiler/) (so I could edit the scopeID without having to register on the repl.it site)
Then copied my scopeID from: Utility/System Setting/System status on the scope menu's to the above python code, pressed Run and up popped up all the keys I needed.
The only slight stumbling block was I had to go from my base 100MHz to 200Mhz, then I had to jump to the 350Mhz key, then on to the final destination 500Mhz, because the others inbetween all produced "Invalid data"
The Bandwidth keys needed a re-boot afterwards, the other options (MSO, MANC and SENT) didn't.
I think you'll need to make sure it's firmware SDS2000X Plus Firmware - 1.3.7R5 just so you make sure all the new decode options are listed (MANC and SENT etc), yes you can do further firmware upgrades afterwards, it won't hurt any options.
-
I am going to buy SDS2104X plus and hack it.
Is there no modification of hardware for hack?
After hack, Can I download firmware of SDS2000X plus? Or do I need to download firmware?
Thanks.
No hardware mods needed, Follow this that I just did and you'll be fine:
So I copied the python code from https://repl.it/@wxq849034624/PrettyAbleGuiltware-1#main.py (https://repl.it/@wxq849034624/PrettyAbleGuiltware-1#main.py)
and pasted it into https://www.programiz.com/python-programming/online-compiler/ (https://www.programiz.com/python-programming/online-compiler/) (so I could edit the scopeID without having to register on the repl.it site)
Then copied my scopeID from: Utility/System Setting/System status on the scope menu's to the above python code, pressed Run and up popped up all the keys I needed.
The only slight stumbling block was I had to go from my base 100MHz to 200Mhz, then I had to jump to the 350Mhz key, then on to the final destination 500Mhz, because the others inbetween all produced "Invalid data"
The Bandwidth keys needed a re-boot afterwards, the other options (MSO, MANC and SENT) didn't.
I think you'll need to make sure it's firmware SDS2000X Plus Firmware - 1.3.7R5 just so you make sure all the new decode options are listed (MANC and SENT etc), yes you can do further firmware upgrades afterwards, it won't hurt any options.
Thanks Zaphod1
In the case firmware version is under 1.3.7R5, then upgrade firmware?
-
Thanks Zaphod1
In the case firmware version is under 1.3.7R5, then upgrade firmware?
Yes, otherwise you won’t see the ‘new’ MANC and SENT decode options that were just added in 1.3.7R5
-
Can you test if the 500MHz is actually working by making some measurements in this range?
You can look there ->
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg2965752/#msg2965752 (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg2965752/#msg2965752)
i have made frequency sweeps
-
Hello fellow engineers,
Do I need a new probe with a higher MHz rating if I hack the unit from 100MHz to 500MHz? SDS210xX Plus 100MHz units ships with 200MHz probes (PP215), but 350MHz unit comes with 350MHz probe (PP2035A).
Perhaps that's a noob question, but what are the drawbacks of measuring let's say a 300MHz signal with a 200MHz probe? What are the artefacts I might (will) observe?
Thanks.
-
If you want to use the full bandwidth with reliable levels, you will indeed need matching probes. A probe rated at x Mhz will have an amplitude error of less than 3 db up to that frequency.
If you use the 200 MHz probe for frequencies above that point, the amplitude of the signal you see is dropped rsp. the rise time is extended.
When you go for a new probe, please check that the compensation range matches the input capacitance of the scope, which is ~17 pF. Higher frequency probes are usually only offered at a 10:1 attenuation. The prices for passive probes range between ~60€ to >500 €. The more expensive ones have a lower capacitance = lower impedance at high frequencies. Go for a probe which has both low and high frequency compensation. The probes delivered with the instruments match typically well.
There was a nice test sequence on probes here in the forum: https://www.eevblog.com/forum/testgear/siglent-sds1104x-e-in-depth-review/msg1434665/#msg1434665 (https://www.eevblog.com/forum/testgear/siglent-sds1104x-e-in-depth-review/msg1434665/#msg1434665)
-
Thanks for a great answer!
The link to the probe test was very informative - it looks like for my particular scope/probe set I'll be fine with 200MHz probes, as it handles the frequency up to 300MHz very well, and I do not need to go beyond that point yet.
-
The PP215 probes, despite the declared 200 MHz band, work well up to 430 MHz (I have not tested with higher frequencies) and have an attenuation comparable to the very expensive 500 MHz Agilent N2890A.
Appearances are deceptive. :)
-
It's called "Promotion".
LOL, yes.
It wasn't showing on the web site when I ordered, but now I've gone back there, the promotion is showing, and because the order actually came direct from Siglent, it seems I automatically got the promotion upgrade :-+
Really only need to do the BW upgrade and I'll be very happy.
Decodes Sent and Manchester should also be licensed as permanent as part of the promo. If you haven't got them licensed contact your supplier with your SN# and Scope ID so they can send you the codes to install.
As FW V1.3.7R5 that added Sent and Manchester was only publicly released after the start of the promotion there will be a few units still sold without these enabled.
I contacted Saelig (from whom I bought my scope) and they said that those two are not included in the promotion. My scope also shows them as temporary licenses.
-
Is there a way to disable an option once it's been enabled? The LCISL command is used to enable an option via SCPI. Is there a corresponding command to disable an option? My search-fu doesn't seem to be good enough to find the answer to this.
-
Is there a way to disable an option once it's been enabled? The LCISL command is used to enable an option via SCPI. Is there a corresponding command to disable an option? My search-fu doesn't seem to be good enough to find the answer to this.
1 Yes, but it's not public. See the attached image.
2 None that I know.
-
Decodes Sent and Manchester should also be licensed as permanent as part of the promo. If you haven't got them licensed contact your supplier with your SN# and Scope ID so they can send you the codes to install.
As FW V1.3.7R5 that added Sent and Manchester was only publicly released after the start of the promotion there will be a few units still sold without these enabled.
I contacted Saelig (from whom I bought my scope) and they said that those two are not included in the promotion. My scope also shows them as temporary licenses.
Unfortunately it indeed seems decodes Sent and Manchester are not part of the current promotion. :(
A few new units across my desk this week didn't have them licensed either.
Latest FW that gave them to us was in Nov whereas the promotion started in Oct so neither are on the free list.
https://siglentna.com/news-article/save-up-to-1764-with-a-new-sds2000x-plus-oscilloscope-and-option-bundle/
-
Is it possible to change the "brand" of the oscilloscope? In Russia, Siglent SDS2104X+ oscilloscopes are localized and distibuted under the "АКИП 4129А" name and have their own ugly download splash screen and a very long inconvenient name Model Name, which is also a template for the name of the all saved files.
Is it possible to bring such a device to the state of the original Siglent SDS2104X+? The devices do not differ in firmware, only Model Name and the boot splash screen.
You can answer the question in the PM.
-
Can you show an image of the model name and the splash screen?
-
No problem :)
The difference from the original SDS2104X+ is only in these three photos. Everything else is unchanged.
The inscriptions on the buttons have also been translated, but I have already resigned myself to this :) Translated, by the way, very competently.
-
Thanks, now please attach your firmdata0\sys_cfg.cfg.
-
Interesting, chinese models, russian and then rest of the world.
I want a german model ;D ;)
No, better not - The translating are mostly bad to read. 8)
now please attach your firmdata0\sys_cfg.cfg.
The "cure" is near....
-
Thanks, now please attach your firmdata0\sys_cfg.cfg.
How can I get this data?
-
My sys_cfg.cfg attached
-
This is the parsing:
Reversing 1st part of the file [00000000-00000CF7]...
XORing with 0xFF (incrementing pattern)...
XORing with 0xFF from 0x0000067C until 0x00000CF7
00000000 - Main Checksum: FFFFB5F9 [00000004-00000CF7] CKSM OK
00000008 - Product_Type: AKIP
00000028 - CFG Type: SDS2000X Plus
0000003C - Manufacturer_Name: ????????
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: AKIP
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: 1800
000000A6 - CFG Flag__lang_total: 11
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: ????????-4129
000000E4 - Machine Name 150 MHz:
000000F3 - Machine Name 200 MHz: ????????-4129
00000102 - Machine Name 250 MHz:
00000111 - Machine Name 300 MHz: ????????-4129
00000120 - Machine Name 50 MHz:
0000012F - Machine Name 70 MHz: ????????-4129
0000013E - CFG Flag___BW_change: 00
0000013F - CFG Flag_hide_set_BW: 01
00000140 - Machine Name 350 MHz: ????????-4129
0000014F - Machine Name 500 MHz: ????????-4129
0000015E - Machine Name 750 MHz: ????????-4129
0000016D - Machine Name1000 MHz: ????????-4129
This is from a "normal" Siglent:
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_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: 1800
000000A6 - CFG Flag__lang_total: 11
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: SDS2104X Plus
000000E4 - Machine Name 150 MHz:
000000F3 - Machine Name 200 MHz: SDS2204X Plus
00000102 - Machine Name 250 MHz:
00000111 - Machine Name 300 MHz: SDS2304X Plus
00000120 - Machine Name 50 MHz:
0000012F - Machine Name 70 MHz: SDS2074X Plus
0000013E - CFG Flag___BW_change: 00
0000013F - CFG Flag_hide_set_BW: 01
00000140 - Machine Name 350 MHz: SDS2354X Plus
0000014F - Machine Name 500 MHz: SDS2504X Plus
0000015E - Machine Name 750 MHz:
0000016D - Machine Name1000 MHz:
So, I suggest your replace your file with the one attached.
Sync and reboot.
Let's see what happens.
-
Somehow I'm afraid. Will it make a brick? There's a possibility?
-
I don't see how that could happen. But it's your call.
-
Ok, thank You! I try replace...
And please, send me /usr/bin/siglent/firmdata0/splash.gif file from "original siglent". This file is the boot splash logo. There is also a 'splash' file (without extension). What is it? Maybe they should be replaced together?
-
First change the cfg. After that we'll deal with the splash.
-
Done!
The 'Мodel' and saved file name template have changed!
It remains to change the splash (it's clear how to do it) and the little banner "AKIP" at the top right of the screen (if it possible).
-
:-+
Now it's time for another member to share their splash image file. I think I don't have one here.
-
tv84, many thanks for the help! :-+
-
By the way, replacing the splash.gif file doesn't change anything. The boot splash screen remains the same. What could be the problem?
-
NAND map:
0x000000000000-0x000000780000 : "fsbl" "BOOT.bin" "mtd0"
0x000000780000-0x000000b80000 : "kerneldata" "uImage" "mtd1"
0x000000b80000-0x000000c00000 : "device-tree" "devicetree.dtb" "mtd2"
0x000000c00000-0x000001100000 : "Manufacturedata"
0x000001100000-0x000001600000 : "reserved1"
0x000001600000-0x000002a00000 : "rootfs"
0x000002a00000-0x000003400000 : "firmdata0" "firmdata0.img" "mtd6"
0x000003400000-0x00000a200000 : "siglent" "siglent.img" "mtd7"
0x00000a200000-0x00000fc00000 : "datafs" "datafs.img" "mtd8"
0x00000fc00000-0x000010000000 : "reserved2" "rootfs.cramfs" "mtd9"
Can you make a NAND dump?
Maybe it is in the "Manufacturedata" MTD.
Or are rendered strings...
-
I don't want to completely lose the warranty by opening the device. Therefore, I cannot make a nand dump. However, if only a splash remains of the localization, it's also not bad, the main thing is that the names of the saved files are now more adequate!
It is strange that the most obvious thing caused difficulties (replacement of a splash)
And I corrected the caption in the upper right corner of the screen. :D
-
tv84, can I dump mtd3 'Manufacturedata' or full NAND dump via telnet without opening the device?
-
I don't want to completely lose the warranty by opening the device.
There are several methods to remove the warranty sticker without damage..
-
A feedback about my unit which was (almost) DOA. I sent it back to the seller mid of December. They waited until Jan 6th to send it back to Siglent Germany. I got a phone call yesterday. The unit is repaired which is good news. The person in charge did not know what the problem was. However, he told me that Siglent noticed that the scope had been hacked :rant: but they concluded that my problem was unrelated to the hack. Thus they repaired the scope under warranty and will get it back to me next week.
:-+
I recently bought 2 units for the lab.I could find some time last Friday to hack them.
it worked well for the 1st unit. I also unlock the second one. Things happened to work flawlessly too but right after the process, the scope simply turned off and never turned on again.
Did anybody face such an issue ?
might be just a doa unit.. if you didnt do anything internally with the OS and was just keys through the UI that wouldnt have caused that
hard call to say if you should even open it up and try the uart port.. if it seems completely dead you are probly better off getting an exchange
-
It is nice from Siglent :-+
-
:-+
Now it's time for another member to share their splash image file. I think I don't have one here.
It is time for a tv84 splash screen 8)
-
However, he told me that Siglent noticed that the scope had been hacked :rant: but they concluded that my problem was unrelated to the hack. Thus they repaired the scope under warranty and will get it back to me next week.
This is a very important thing to know and should be marked on top - Thankyou for sharing !!!! :-+
-
Just purchased a SDS2104x PLUS , (and it came with SDS2000X Plus Firmware - 1.3.7R5 )
[...]
Scope now reports on screen as a SDS2504X PLUS , I didn't need to go near a computer connection, all done on the 'scope screen.
+1
Still seems to work fine. :-)
Thx a lot!
-
Has anybody figured out the splash screen yet?
-
Here is a script to do a NAND dump. (copied from the SVA one)
Not tested yet.
Don't blame me if anything explodes!
-
tv84, thanks! I need to get up the courage and decide to bet $ 2,000 :-DD
I'll think about whether it's worth the risk to replace the splash screen :)
-
Hi, I bought SDS2102X+ Software updated to 1.3.7R5. Successfully updated to 200MHz so now there is written SDS2202X Plus in "System Setting".
How to upgrade to 350MHz? There is no "Option Type" in "Options" menu I can chose and where to put the key I have.
I tested 470MHz sinus and I can see the wave correctly so I do not understand what will change after 350MHz upgrade but if possible I want to test it.
Thanks.
-
use SCPI commend "MCBD", e.g. "MCBD your BW-Key" and send
-
use SCPI commend "MCBD", e.g. "MCBD your BW-Key" and send
I quickly study what SCPI is, then installed NI-VISA as written in "Programing guide" and tested to send MCBD and my BW-Key - It works!
Now there is written SDS2352X in System Status - Thank you KeBeNe !
-
use SCPI commend "MCBD", e.g. "MCBD your BW-Key" and send
I quickly study what SCPI is, then installed NI-VISA as written in "Programing guide" and tested to send MCBD and my BW-Key - It works!
Now there is written SDS2352X in System Status - Thank you KeBeNe !
:-//
Why, when the scope has an internal webserver that includes a SCPI command panel.
-
simply because I do not know my new oscilloscope enough :-)
But why the Amplitude measuring is not correct? At sinus signal it is half of the Pk to Pk value. I tested AC DC Coupling but allays the same result. Is it Peak-to-peak amplitude the oscilloscope usually measure?
BTW, No changes in machine after upgrade from 2202 to 2352 All signals looks exactly same as before.
-
peak to peak does mean -50 to +50mV, which is 100mV in total. So everything ist fine.
-
But why the Amplitude measuring is not correct? At sinus signal it is half of the Pk to Pk value. I tested AC DC Coupling but allays the same result.
Huh?
Even though this is off topic, I still want to say this:
1. Pk-Pk ~100mV is obviously correct (because the signal amplitude is 5 divisions on the screen at 20 mV/div)
2. Amplitude (as well as Top and Base) is a measurement NOT applicable for sine waves, only meant for squarewave and pulses.
3. Even so, Amplitude measurement is not far off and appears to be easily within even the DC accuracy specs (despite being a 10 MHz signal) - yet another strong reason to NOT complain.
EDIT: For those wondering (and unwilling to RTFM):
Pk-Pk and Amplitude are almost the same measurement, but Pk-Pk includes the overshoot in rectangular waveforms, whereas Amplitude only uses the flat top and base.
-
Does anybody know what exactly will change after BW upgrade? I cannot recognize any difference. It looks like nothing is better. If the signal was deformed now is deformed at the same way. I could see frequency 470MHz even if the bandwidth was 200MHz only. Horizontal scale was and is 1ns/div and there are 2 measure point in 1ms witch represents 2GSa/s. So what exactly means 350MHz bandwidth and what has changed comparing 200MHz BW?
BTW which of signal is correct??? - same signal I only changed input resistance and bits resolution on oscilloscope. I did not touch generator. (connection by RG58U cable)
-
Does anybody know what exactly will change after BW upgrade? I cannot recognize any difference.
You won't unless you have an accurate and level high frequency signal source.
Scope BW is specified when a sine wave is 3dB down.
Eg a 1V sinewave = 0.707V on the instrument.
For a 350 MHz DSO this would be expected at ~400 MHz +~30 MHz.
-
Hi,
Maybe I´m too lazy to read the last pages (no, I am lazy..), but how could I make the two new decoder types licensig forever with the generator mentioned in post#1 ?
Martin
-
Maybe I´m too lazy to read the last pages (no, I am lazy..), but how could I make the two new decoder types licensig forever with the generator mentioned in post#1 ?
Use "SENT" and "MANC" (plus SCOPEID) to create the keys. If entry in sccope fails (due to bug with last option), use LCSIL with comma (!) through SCPI interface.
E.g.
LCISL MANC,<key>
-
Does anybody know what exactly will change after BW upgrade? I cannot recognize any difference. It looks like nothing is better. If the signal was deformed now is deformed at the same way. I could see frequency 470MHz even if the bandwidth was 200MHz only. Horizontal scale was and is 1ms/div and there are 2 measure point in 1ms witch represents 2GSa/s. So what exactly means 350MHz bandwidth and what has changed comparing 200MHz BW?
BTW which of signal is correct??? - same signal I only changed input resistance and bits resolution on oscilloscope. I did not touch generator. (connection by RG58U cable)
You wanted to say ns, not ms, right?
You did not deliberately attach screenshots that don't have enough resolution to clearly see the parameters, did you?
You have had a look into the manual, haven't you? Still you've obviously missed the part where it says that 10 bit mode is always limited to 100 MHz bandwidth ;)
Even with the blurred screenshots, I think I can see there is not 1 ns/div, let alone 1 ms/div, but rather 5 ns/div and the signal frequency might be around 50 MHz.
Now for the question about the "correct" signal, assuming the goal is to see a difference between 200 and 350/500 MHz bandwidth.
1. This rules out 10 bit mode already - because it is always just 100 MHz.
2. Fundamental signal theory rules out the 1M (aka High-Z) "measurements" as well, because we cannot expect any signal fidelity/accuracy with a severly mismatched connection.
So what remains?
Correct, it is the properly terminated (50 ohms) 8 bit setup!
Finally the most obvious verification step would be to look at a fast signal with and without the 200 MHz bandwidth limit. The attached screenshots show this for a 50 MHz squarewave with 1 ns rise/fall times. In this case it is the difference between 200MHz (nom.) and 500 MHz (nom. – in actual fact it is about 620 MHz!).
EDIT: The issue with the screenshots was on my side, sorry for the rant.
-
I tested upgrade to bandwidth 500MHz. It is written on Siglent pages that my origin model SDS2102 can not be upgraded to 500MHz but it looks like it is possible. Now there is written SDS2502X Plus in System Setting.
Thanks to Performa01 I realized there is new menu in Channel/BW Limit: 20M/200M/Full so I can compare 200M vs 500MHz BW. (In SDS2102 there was only 20M/Full) Horizontal scale is now 500ps/div
So finally I can write Yes there is difference after BW upgrade. Thanks to all.
-
I tested upgrade to bandwidth 500MHz. It is written on Siglent pages that my origin model SDS2102 can not be upgraded to 500MHz but it looks like it is possible. Now there is written SDS2502X Plus in System Setting.
Well, that might be a deliberate marketing decision. A 4-channel 350 MHz scope is still a 2-channel scope if you want to utilize the 500 MHz bandwidth. But for the 2-channel variant such as the SDS2102, you can use only one channel if you want the full 500 MHz bandwidth - and Siglent quite obviously didn't think this would be a viable offer.
Hackers on the other hand, they just don't care ;)
So finally I can write Yes there is difference after BW upgrade. Thanks to all.
:-+
-
Well, that might be a deliberate marketing decision. A 4-channel 350 MHz scope is still a 2-channel scope if you want to utilize the 500 MHz bandwidth. But for the 2-channel variant such as the SDS2102, you can use only one channel if you want the full 500 MHz bandwidth - and Siglent quite obviously didn't think this would be a viable offer.
Exactly, I just tested it. If I turn on both channels, BW is 350MHz only.
-
Just purchased a SDS2104x PLUS , (and it came with SDS2000X Plus Firmware - 1.3.7R5 )
So I copied the python code from https://repl.it/@wxq849034624/PrettyAbleGuiltware-1#main.py (https://repl.it/@wxq849034624/PrettyAbleGuiltware-1#main.py)
and pasted it into https://www.programiz.com/python-programming/online-compiler/ (https://www.programiz.com/python-programming/online-compiler/) (so I could edit the scopeID without having to register on the repl.it site)
Then copied my scopeID from: Utility/System Setting/System status on the scope menu's to the above python code, pressed Run and up popped up all the keys I needed.
The only slight stumbling block was I had to go from my base 100MHz to 200Mhz, then I had to jump to the 350Mhz key, then on to the final destination 500Mhz, because the others inbetween all produced "Invalid data"
The Bandwidth keys needed a re-boot afterwards, the other options (MSO, MANC and SENT) didn't.
Scope now reports on screen as a SDS2504X PLUS , I didn't need to go near a computer connection, all done on the 'scope screen.
Thanks to all concerned. :-+
Just wanted to note that as of Feb 21, the above works just fine. Brought my 2104x+ up to a 2504x+ without incident.
I'm no scope expert, but to chime in on bandwidth expectations...
1) 8-bit mode. This is called out in the manual and a number of time in this thread.
2) Probes. The 2104X+ comes with 200MHz probes. This will impact measuring even a 50MHz square wave, to a degree.
3) matching/termination. Also called out elsewhere. If you are doing bandwidth tests, 50Ohm termination with proper matched coax and signal source. Also note that 50ohm termination can impact the signal level depending on your signal source. IIRC Dave did a video on this subject.
4) Sampling rate. This is a big thing on this scope. With a single channel enabled, you get 2Gs/s. At 500Mhz, thats only 4 samples per cycle. Trying to look at anything other than a sine wave, or something very close to it, is going to give you a poor representation of the signal. Signal interpolation only does so good. If you turn on both channels on the same ADC (1+2/3+4), the same rate drops to 1Gsa/s. That's not enough for 500MHz, full stop. Calling it good for 350MHz is a stretch. 250Mhz gets you the same 4x sampling that you had with a single channel at 500MHz.
For waveforms, the 2504x+ is, IMHO, a 200MHz (1 channel), 100MHz (2 channel) scope. Above that, you need to know what you are doing and how to interpret what you are seeing as sample rates start to limit representation. Where the 500Mhz bandwidth will help to a degree, is with representing high frequency components of slower wave forms -- the aforementioned 50MHz square wave. Even that is dependent on your probing setup.
-
By the way, the supplied 200MHz probes actually have a bandwidth of about 350MHz and a real 1nS rise time! Despite the unprepossessing look and marking "200 MHz".
A rare case when the manufacturer's declared characteristics are worse than real! :)
-
2) Probes. The 2104X+ comes with 200MHz probes. This will impact measuring even a 50MHz square wave, to a degree.
Even the most expensive passive high-impedance probe with the widest bandwidth rating will not have a perfectly flat frequency response, thus impact measurements to a degree indeed.
Apart from that, how do you know this? Have you ever measured the system bandwidth with the supplied probes?
3) matching/termination. Also called out elsewhere. If you are doing bandwidth tests, 50Ohm termination with proper matched coax and signal source. Also note that 50ohm termination can impact the signal level depending on your signal source. IIRC Dave did a video on this subject.
No. It can not impact the signal level, it will impact the signal level. To be more precise, it will halve the signal level when compared to the High Z termination. This is so because the source impedance will be 50 ohms (if it's not, then we don't have a proper matched signal source anymore).
4) Sampling rate. This is a big thing on this scope. With a single channel enabled, you get 2Gs/s. At 500Mhz, that' only 4 samples per cycle. Trying to look at anything other than a sine wave, or something very close to it, is going to give you a poor representation of the signal. Signal interpolation only does so good.
Big thing? This scope? Only good for sine waves? Now fasten your seat belts: any scope (analog or digital) will only be able to properly display and analyze sine waves as soon as you exceed half its bandwidth. Surprise, surprise!
So it all comes down to the (obvious) fact, that for non-sinusoidal signals, much more bandwidth is needed than just covering the fundamental frequency. There have been rules of thumb for almost forever, how for example you should have at least 5 times the bandwidth for a square wave – 7 or even 9 times is better of course. It all comes down what you want to see and measure, i.e. the exact shape of a waveform is often not important, we just want to know the amplitude and where the transitions (i.e. zero crossings) are.
Only 4 samples per cycle? And what does the sampling theorem request?
Do you have test results that indicate that 4 samples per cycle aren't sufficient to reproduce a sine wave?
In theory, we need just 2 samples per cycle. Theory exists only in textbooks, as we all know, so practice is different indeed. Some decades ago, early realtime sampling DSOs like Tek TDS220 could only have 100 MHz bandwidth despite a 1 GSa/s sample rate, just because they only had linear interpolation instead of a proper sin(x)/x reconstruction. Digital signal processing just was not very common back then. As a result, a sample rate ten times higher than the maximum signal frequency was indeed a requirement.
In order to come close to the theory, we need a few things; one of them a proper reconstruction (not interpolation!) at the output of the sampling system. Since this system is not only sampling, but also digital, we have the opportunity to have our reconstruction filter in the digital domain as part of the digital signal processing chain. This means, we can have a FIR filter with near ideal brickwall characteristics and constant group delay. Or should I better say: we could have it, if the number of data points would be infinite. Instead of this, we just have a couple samples per screen width at short timebase settings. This means we cannot go straight to Nyquist, e.g. 500 MHz bandwidth at 1 GSa/s samplerate, it is not the factor of 2.0 from the textbook, but rather 2.5. This means that in today’s DSOs, 1 GSa/s is good for up to 400 Mhz.
If you turn on both channels on the same ADC (1+2/3+4), the same rate drops to 1Gsa/s. That's not enough for 500MHz, full stop. Calling it good for 350MHz is a stretch. 250Mhz gets you the same 4x sampling that you had with a single channel at 500MHz.
Once again I read wild claims – do you have any evidence that 350 MHz is “a stretch”?
The cheap Siglent SDS2000X+ gives you the option to use it up to 500 MHz in half-channel mode. Only in this mode, the input bandwidth is 500 MHz; as soon as the sample rate drops to 1 GSa/s, the input bandwidth is limited to 350 MHz. All this is clearly indicated in the input channel tabs.
Of course the input bandwidth limit is not very effective - it is only 1st order. We cannot have anything more effective in the analog domain, because more than anything else we need a constant group delay in a scope frontend. Consequently, an effective AA filter is not going to happen, but in practice we can live with that quite well.
For waveforms, the 2504x+ is, IMHO, a 200MHz (1 channel), 100MHz (2 channel) scope. Above that, you need to know what you are doing and how to interpret what you are seeing as sample rates start to limit representation. Where the 500Mhz bandwidth will help to a degree, is with representing high frequency components of slower wave forms -- the aforementioned 50MHz square wave. Even that is dependent on your probing setup.
There is a clear definition: The bandwidth of any scope is where the amplitude of a sine wave drops by 3 dB.
Other than that you are still caught in the (early) nineties of last century, where a factor of ten for sample rate to bandwidth was indeed mandatory – even though with ridiculously short memories like the 2.5k in a TDS220, the sample rate (hence also the bandwidth) drops like a stone for time bases any slower than ~200 ns/div…
It would be much more appropriate to worry about aliasing, because the input bandwidth limit isn’t very effective (it just cannot be) and so we only have a weak AA filtering. This means you can provoke aliasing artefacts if you throw signals with a much wider bandwidth than 500 MHz at the scope in full channel mode.
With fast signals that have a wide spectrum, vastly exceeding 500 MHz, you can indeed provoke aliasing artefacts in full-channel mode, i.e. at only 1 GSa/s. But rest assured that you won’t be able to do the same in half-channel mode at 2 GSa/s, even though the true input bandwidth is 570 MHz then. Anything that goes beyond Nyquist, i.e. > 1GHz is already sufficiently attenuated so aliasing won’t be a problem.
Finally I agree: it’s always desirable if you know what you are doing. Above but also below 100 or 200 MHz.
-
it is not the factor of 2.0 from the textbook, but rather 2.5. This means that in today’s DSOs, 1 GSa/s is good for up to 400 Mhz.
See also here:
https://de.tek.com/document/application-note/real-time-versus-equivalent-time-sampling
-
here i play with an SDS2204X
I also upgraded from originally 200MHz to 350 MHz and then again to 500 MHz,
before, and after each upgrade i performed some bw test,
and see the attached results :-) it actually works,
it even trigger and show signals over 1GHz too :-)
[attachimg=1]
-
I am getting ready to pull the trigger on an SDS2104X Plus. The current promotion from Siglent includes all options (minus MSO) which, aside from AWG, I would likely never need anyway. The only one that may be enticing to me sometime in the future would be the BW upgrade.
Regarding ‘upgrading’ the scope, I’ve read this thread and the entire SDS2000X Plus thread, and I understand the following:
- All SDS2000X Plus model variants use identical hardware;
- There are two viable methods for ‘upgrading’: (i) via Telnet; or (ii) through generating licence keys in Python;
- Opening up the scope to get physical access to the circuits is not necessary;
- Firmware version 1.3.7R5 is still ‘upgradeable’;
- Updating the firmware to future versions would not invalidate the ‘upgrades’, i.e. the ‘upgrades’ are permanent;
- Once ‘upgraded’, the options could not be deactivated or rolled back (it would actually be possible but the method is not public);
- However, once ‘upgraded’, the BW could be downgraded to another BW or to the original BW configuration, e.g. by using the corresponding licence key generated in Python; and
- ’Upgrading’ the scope would void the warranty.
Is my understanding above correct? Would there be anything else to add that I should know or be aware of? Thanks.
-
if 7 is true, 8 will be false ?
or if you dial in the correct codes, it dont matter where they came from, the unit is correctly upgraded, right ?
-
Hi,
’Upgrading’ the scope would void the warranty.
Yes and no.... (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-hack/msg3427904/#msg3427904) ;)
the unit is correctly upgraded, right ?
Right.
-
Therefore... are all my eight statements true? (I understand there may be some manufacturer ‘flexibility’ on item #8.)
-
Regarding ‘upgrading’ the scope, I’ve read this thread and the entire SDS2000X Plus thread, and I understand the following:
- All SDS2000X Plus model variants use identical hardware;
- There are two viable methods for ‘upgrading’: (i) via Telnet; or (ii) through generating licence keys in Python;
- Opening up the scope to get physical access to the circuits is not necessary;
- Firmware version 1.3.7R5 is still ‘upgradeable’;
- Updating the firmware to future versions would not invalidate the ‘upgrades’, i.e. the ‘upgrades’ are permanent;
- Once ‘upgraded’, the options could not be deactivated or rolled back (it would actually be possible but the method is not public);
- However, once ‘upgraded’, the BW could be downgraded to another BW or to the original BW configuration, e.g. by using the corresponding licence key generated in Python; and
- ’Upgrading’ the scope would void the warranty.
Hi,
1. Yes, except the lost of 2 additional channels on the 2-ch model
2. Yes.
3. Yes.
4. Yes, because (my thoughts on it) you type in "real" license keys as if you would get them from official side
5. Yes, unlikely the pain the rigol 5000 user gets, these "upgrades" are permanent. 8)
6. Yes and yes... ;)
7. I only know upgrading, never try to downgrade the bandwith
8. As I said before, they detect it (easily by the SN, I guess) but they claimed, the error doesn´t result from the hack, so repair under warranty is possible. In THIS case...
Martin
-
I'm pretty sure that the bandwidth can be also downgraded with the same SCPI command that's used for upgrading (not through the menu obviously).
Removing options is said to be possible somehow, but there is no obvious way for this as for downgrading the bandwidth.
-
Removing options is said to be possible somehow, but there is no obvious way for this as for downgrading the bandwidth.
One has to reach this menu.
-
Does anyone know if the hack works with the SDS2102X plus two channel? I signed up with Replit and used the keygen link from the first post. Changed the scope ID to match mine and ran it. I am unable to get any of the keys to work by entering them in lower or upper case. I noticed that someone indicated they had to upgrade progressively starting with 100 MHz. That didn’t work either but the only bandwidth option I have available on the scope is 2BW03. Any suggestions will be very much appreciated.
-
Does anyone know if the hack works with the SDS2102X plus two channel?
It works.
-
Wasn't it like that You have started with bw02 option (or whatever for 200M), and now you have turned it on, so next is 350M?
-
If you use the SCPI MCBD command you don't need nothing of that.
You can simply do:
MCBD <lic_500M>
-
I noticed that someone indicated they had to upgrade progressively starting with 100 MHz. That didn’t work either but the only bandwidth option I have available on the scope is 2BW03. Any suggestions will be very much appreciated.
There is no 200MHz option for the 2 channel scope that I can see. Only the 4 channel scope. 2BW03 upgrades directly from 100 MHz to 350 MHz.
https://siglentna.com/product/bandwidth-upgrade-100-to-200-mhz-2-channel-models/ (https://siglentna.com/product/bandwidth-upgrade-100-to-200-mhz-2-channel-models/)
In my searches I found 4 different Python scripts that produced 4 different sets of keys. If at first you don't succeed...
-
The only BW option mine has ever had is 2BW03. It's also the only SDS2102X+ upgrade option available for purchase that I saw.
-
Thank you very much. This is in an area I know nothing about. Can this be performed with NI-VISA that the Siglent programming manual refers to?
-
Thank you! I only tried one. I'll search for the others and give them a try.
-
Using the VISA test panel basic I/O I sent MCBD <lic_500M> to the scope. It returned so many bytes of data. I assume that this is data returned from the scope? As soon as I hit write or click elsewhere on the screen, my entered command is changed to MCBD\s<lic_500M>?. I recycled power and did not see any changes in the options. I just got called into work but later I'll see what the the half power frequency is. If the command worked would it have changed the bandwidth option or the model number? Thank you!
-
Thank you very much. This is in an area I know nothing about. Can this be performed with NI-VISA that the Siglent programming manual refers to?
Roy please use the Quote button so we can see who you are replying to.
No need to use anything but the scopes webserver and its SCPI command page. Option codes can be entered from the webserver also and it's easy to Copy/Paste them into the input box in the Options page when in Instrument Control.
As mentioned earlier option codes are all lower case.
When doing any of this for customers that buy options it takes only a few minutes when connected to a PC using the scopes webserver.
-
Thank you very much. This is in an area I know nothing about. Can this be performed with NI-VISA that the Siglent programming manual refers to?
Roy please use the Quote button so we can see who you are replying to.
No need to use anything but the scopes webserver and its SCPI command page. Option codes can be entered from the webserver also and it's easy to Copy/Paste them into the input box in the Options page when in Instrument Control.
As mentioned earlier option codes are all lower case.
When doing any of this for customers that buy options it takes only a few minutes when connected to a PC using the scopes webserver.
Thank you tautech. As soon as I saw your message I looked at the thread and saw what a mess I made. Sorry about that to everyone. I have not been on a forum in many years. The web server is great! I like how you can operate the scope from it too. Unfortunately, it didn’t work either. The command takes so it must be something I am doing wrong with the script or I need to find a different one. The only thing I am changing on it is the scope ID. I am entering exactly how it’s shown on the scope with the hyphens so it looks like this: ‘SCOPEID = '1800-2be1-3e0a-2ca1'. I made 100% sure when I copied the key into lower case that It’s correct.
-
Thank you very much. This is in an area I know nothing about. Can this be performed with NI-VISA that the Siglent programming manual refers to?
Roy please use the Quote button so we can see who you are replying to.
No need to use anything but the scopes webserver and its SCPI command page. Option codes can be entered from the webserver also and it's easy to Copy/Paste them into the input box in the Options page when in Instrument Control.
As mentioned earlier option codes are all lower case.
When doing any of this for customers that buy options it takes only a few minutes when connected to a PC using the scopes webserver.
Thank you tautech. As soon as I saw your message I looked at the thread and saw what a mess I made. Sorry about that to everyone. I have not been on a forum in many years. The web server is great! I like how you can operate the scope from it too. Unfortunately, it didn’t work either. The command takes so it must be something I am doing wrong with the script or I need to find a different one. The only thing I am changing on it is the scope ID. I am entering exactly how it’s shown on the scope with the hyphens so it looks like this: ‘SCOPEID = '1800-2be1-3e0a-2ca1'. I made 100% sure when I copied the key into lower case that It’s correct.
No Hyphens required. ;)
Even when using the webserver for installing options the codes can be just Copy/Pasted and the scopes UI just sorts it out. :)
-
Thank you very much. This is in an area I know nothing about. Can this be performed with NI-VISA that the Siglent programming manual refers to?
Roy please use the Quote button so we can see who you are replying to.
No need to use anything but the scopes webserver and its SCPI command page. Option codes can be entered from the webserver also and it's easy to Copy/Paste them into the input box in the Options page when in Instrument Control.
As mentioned earlier option codes are all lower case.
When doing any of this for customers that buy options it takes only a few minutes when connected to a PC using the scopes webserver.
Thank you tautech. As soon as I saw your message I looked at the thread and saw what a mess I made. Sorry about that to everyone. I have not been on a forum in many years. The web server is great! I like how you can operate the scope from it too. Unfortunately, it didn’t work either. The command takes so it must be something I am doing wrong with the script or I need to find a different one. The only thing I am changing on it is the scope ID. I am entering exactly how it’s shown on the scope with the hyphens so it looks like this: ‘SCOPEID = '1800-2be1-3e0a-2ca1'. I made 100% sure when I copied the key into lower case that It’s correct.
No Hyphens required. ;)
Even when using the webserver for installing options the codes can be just Copy/Pasted and the scopes UI just sorts it out. :)
Thank you very much!!! I just finished quite a bit of reading from the forum. I now realize where you work and it will not be forgotten. Thanks to all of you for your help. I have spent the last two weeks off and on nearly pulling my hair out trying to get this to work. I had read someone say “to change bandwidth, use scpi command MCBD hexkey” but the keys I was getting were not in hex. After some research I installed python & IDLE to my disappointment the exact same keys were generated. I tried entering every which way and sequence I could think of. The ONLY thing I didn’t think to try was eliminating the dashes! Thanks again to all for taking the time. It is very much appreciated.
I am not sure if they are all this way but I am convinced my SDS2102X had a 200 MHz bandwidth out of the box. The amplitude was exactly 30% down at 200 MHz.
-
Thank you very much. This is in an area I know nothing about. Can this be performed with NI-VISA that the Siglent programming manual refers to?
Roy please use the Quote button so we can see who you are replying to.
No need to use anything but the scopes webserver and its SCPI command page. Option codes can be entered from the webserver also and it's easy to Copy/Paste them into the input box in the Options page when in Instrument Control.
As mentioned earlier option codes are all lower case.
When doing any of this for customers that buy options it takes only a few minutes when connected to a PC using the scopes webserver.
Thank you tautech. As soon as I saw your message I looked at the thread and saw what a mess I made. Sorry about that to everyone. I have not been on a forum in many years. The web server is great! I like how you can operate the scope from it too. Unfortunately, it didn’t work either. The command takes so it must be something I am doing wrong with the script or I need to find a different one. The only thing I am changing on it is the scope ID. I am entering exactly how it’s shown on the scope with the hyphens so it looks like this: ‘SCOPEID = '1800-2be1-3e0a-2ca1'. I made 100% sure when I copied the key into lower case that It’s correct.
No Hyphens required. ;)
Even when using the webserver for installing options the codes can be just Copy/Pasted and the scopes UI just sorts it out. :)
Thank you very much!!! I just finished quite a bit of reading from the forum. I now realize where you work and it will not be forgotten. Thanks to all of you for your help. I have spent the last two weeks off and on nearly pulling my hair out trying to get this to work. I had read someone say “to change bandwidth, use scpi command MCBD hexkey” but the keys I was getting were not in hex. After some research I installed python & IDLE to my disappointment the exact same keys were generated. I tried entering every which way and sequence I could think of. The ONLY thing I didn’t think to try was eliminating the dashes! Thanks again to all for taking the time. It is very much appreciated.
I am not sure if they are all this way but I am convinced my SDS2102X had a 200 MHz bandwidth out of the box. The amplitude was exactly 30% down at 200 MHz.
First up I work for myself as NZ distributor.
Yes hexkey is wrong when all option codes are alphanumeric.
SDS210* Plus models are 100 MHz BW rated however tests have shown they are ~185 MHz at their -3dB point.
(1V p-p in for 0.707mV measured)
Enjoy your scope. :)
-
This is my first post at eevblog. Does anyone have issue to open the keygen link in the thread? Somehow I get the message below:
Woah! Looks like this repl needs an owner.
There is also a Lauszus/main.py at github. Are they the same? Thanks.
-
This is my first post at eevblog. Does anyone have issue to open the keygen link in the thread? Somehow I get the message below:
Woah! Looks like this repl needs an owner.
There is also a Lauszus/main.py at github. Are they the same? Thanks.
Welcome to the forum.
It is locked to changes on the GitHub page.
So you need to copy the code to a local running instance of Python on your PC or Mac / Linux machine, and then edit as needed and run.
-
This is my first post at eevblog. Does anyone have issue to open the keygen link in the thread? Somehow I get the message below:
Woah! Looks like this repl needs an owner.
There is also a Lauszus/main.py at github. Are they the same? Thanks.
Welcome to the forum.
It is locked to changes on the GitHub page.
So you need to copy the code to a local running instance of Python on your PC or Mac / Linux machine, and then edit as needed and run.
Thanks a lot for the confirmation. The scope becomes so popular that it's hard to find it in stock. My order won't be shipped until two weeks later.
-
This is my first post at eevblog. Does anyone have issue to open the keygen link in the thread? Somehow I get the message below:
Woah! Looks like this repl needs an owner.
There is also a Lauszus/main.py at github. Are they the same? Thanks.
Welcome to the forum.
It is locked to changes on the GitHub page.
So you need to copy the code to a local running instance of Python on your PC or Mac / Linux machine, and then edit as needed and run.
Thanks a lot for the confirmation. The scope becomes so popular that it's hard to find it in stock. My order won't be shipped until two weeks later.
Codes for my scope were generated by python for Android. For some it may be easier and more convinient than playing with it on pc.
You say, that scope is difficult to find. Better look for decent 500M probes, before they all gone or skyrocket with price...
-
I´ve bought "premium" but old used 350Mhz Probes - They are ways beyond my needs in every case... ;)
-
I´ve bought "premium" but old used 350Mhz Probes - They are ways beyond my needs in every case... ;)
I've seen that. Tried to to do the same, but few months later... No luck. Ended with 500M probes, that have cost me about 300 euro for set of four...
-
I just purchased an SDS2104X Plus, at Software 1.3.7R5, FPGA 2020-09-23, CPLD 03, Hardware 02-04. Using "SDS2000X+" for Model, SCOPEID sans hyphens in dual case, options updates went trivially easily.
Note, I don't see much difference with the 500MHz update except the 0.5nS/Div horizontal position and less high-frequency cutoff than at 350MHz. It's interesting to have more than one choice for limited bandwidth! (Was On/Off, Now Full/20M/200M).
Picture is a fast-rise-time pulse (avalanche 2n3904 at 160V). The peak at 350MHz (11.25V) was a little smaller than at 500MHz (13.6V). With only 10 dots on the entire screen, I'm not certain how useful the 0.5nS/Div setting is, but it makes my 5nS-rise-time signal generator (SDG1062X) ramp look quite flat!
-
Nice!!
Curious about your 2N3904 avalanche pulse generator. Did you use a slow HV ramp (~1KHz) with a ~160V peak voltage to avalanche the collector base junction? Reason I'm asking is I've developed a high voltage (+-175V) dual amp for use as a AWG HV amplifier and one use was considering it as a "driver" for an avalanche fast edge pulse generator.
Best,
-
Well the price of video cards is now almost what would pay for a sds2104x+
So now I have a new scope to set my sights on, as long as the hack still works.
-
Well the price of video cards is now almost what would pay for a sds2104x+
So now I have a new scope to set my sights on, as long as the hack still works.
Not sure if you are waiting for confirmation here? Nothing has changed in that regard.
-
I was able to get all options 'permanentified.'
Bandwidth upgraded in steps from 200MHz and up, skipped some steps in between because not all of the subsequent steps would allow the option to be activated.
Some of the options were not in the published python script, in which case I simply added that option to the script in a format similar to the that used for the options already in the script.
The "MANCH" option is tricky in that it doesn't follow the same naming convention as the other options. The options are truncated to max 4 characters, so use "MANC" in the script which yields a working code.
Big thank you to whoever decoded this stuff.
-
Hi,
Got a pm a few weeks ago:
I am very happy if you can guide me to whatever I need in order to upgrade my coming Siglent.
I think I do it better here, so people can correct me, if I´m wrong... ;)
Taken some screenshots listed below, according to the "guide" step by step.
First you have to open the link mentioned in the very first post here.
Second you got the message like in pic 2, you have to login to continue.
Third I use my google-account for loggin in.
Fourth and fifth, you are now into the program, where you have to erase the "zeros" in SCOPE ID and fill in the ID of your scope.
Then press "Run"...
Sixth now you got a couple of license keys which you have to enter in the options menu.
The several bandwith license key are making no sense except the ones for 200,350 and 500Mhz.
This was it.
Or don´t you agree, gentlemen here ? ;)
Therefore I wrote it here...
Martin
-
If I applied the BW option code for 350 MHz and later find that 100 MHz are sufficient for my projects, I understand that I can go back by entering a 100 MHz license code. But would it be possible somehow to find out (e.g. by a repair technician), that I had applied another code before? What about the 500MHz code (which removes the BW option from the menu)?
Thanks again,
Anik
-
Hi,
Maybe some other guy did the same mistake as I did a few minutes before, so this is a reminder... :D
Regarding to the keygen, scope id means scope id, NOT scope serial number.... :P
I was wondering why the generated keys looked so different to the ones I´ve installed (and backing it up in a txt file)...
Problem was 30cm before the screen.. 8)
Wanted to install the 2 last open licenses, Sent and Manchester.
So I´ve edited 'SENT' and 'MANC' in the options with no problem.
Run it, install it and done.
Martin
-
Hi all,
I was so impressed with the SSA3021X plus (now liberated to a SVA1032X) that I ordered the SDS2104X plus, also to make use of the Logic analyser probe offer and the Batterfly November extra 10% discount.
Anyway, I ran the Python script and the scope now thinks it's a 2504X, with all options permanent. Now the question, does it makse sense to enter the 750M or 1000M code? (I had to go 100M->350M->500M to have the keys accepted, with a reboot in between.)
More than happy to leave it at 500M it doesn't make any sense or the frontend can't handle it.
-
Hi all,
I was so impressed with the SSA3021X plus (now liberated to a SVA1032X) that I ordered the SDS2104X plus, also to make use of the Logic analyser probe offer and the Batterfly November extra 10% discount.
Anyway, I ran the Python script and the scope now thinks it's a 2504X, with all options permanent. Now the question, does it makes sense to enter the 750M or 1000M code? (I had to go 100M->350M->500M to have the keys accepted, with a reboot in between.)
More than happy to leave it at 500M it doesn't make any sense or the frontend can't handle it.
None at all as the X Plus is just a 500 MHz design whereas those codes are better suited to the 1 GHz design of SDS5000X.
Enjoy your new scope. :)
-
Hi eveyrone and happy Christmas!
So, i wanted to gift myself an sds2104x plus this year, does anybody knows if the keys are valid with the new firmware 1.3.9R6?
Does the firmware version makes any difference? And if it does, is it possible to downgrade to a version which is hackable?
-
Hi,
Wasn´t and shouldn´t be a problem, actually.
You entry "true" license keys and "permanent" means permanent, regardless of the fw.
-
Hi eveyrone and happy Christmas!
So, i wanted to gift myself an sds2104x plus this year, does anybody knows if the keys are valid with the new firmware 1.3.9R6?
Does the firmware version makes any difference? And if it does, is it possible to downgrade to a version which is hackable?
Apparently the keygen doesn't work with the new firmware 1.3.9R6. I just tried it, and none of the keys generated work...
-
I´ve done this here (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-hack/msg3829499/#msg3829499) with the latest firmware...
-
OK, I think I have it, I entered the HEX scope ID including the - marks, that generated wrong keys.
Thanks for the help.
-
:-+
-
Hi all.
How do I get keys for SDS2102X (without Plus) ?
-
I´ve done this here (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-hack/msg3829499/#msg3829499) with the latest firmware...
Hi all,
I've a simple question, It's possbile to downgrade oscilloscope's firmware e.g. 1.3.7R5 ?
Sure, It worked with latest firmware version. however, Could be ane extra option, first downgrade firmware, "do the trick" and then upgarde.
cheers!
-
https://www.eevblog.com/forum/testgear/siglent-sdg2042x-hack-door-closed/msg4018144/#msg4018144 (https://www.eevblog.com/forum/testgear/siglent-sdg2042x-hack-door-closed/msg4018144/#msg4018144)
-
My SDS2104X+ scope has just come with the firmware version is 1.3.9R10.
Release notes say that the difference is compatibility with the new hardware revision (04-05).
Does anyone know what is changed with this new hardware revision and if the hack is compatible with this firmware?
-
My SDS2104X+ scope has just come with the firmware version is 1.3.9R10.
Interesting note for 1.3.9R10:
This release cannot be downgraded to former releases.
Could this be the enabling of dynamic key for SDS2k+?
Perhaps you could check, like in this discussion?
1.3.9R6
In your NSP_system_info.xml is there any reference to a "Dynamic Key"?
-
Seems like it does not contain any dynamic key
-
Seems like it does not contain any dynamic key
Nice, guess the downgrade protection is just a failsafe to keep people with the new hardware from bricking their device then.
Wonder too what the difference is.
Anyway, can't see any reason why the existing python script wouldn't work for you.
-
Seems like it does not contain any dynamic key
Nice, guess the downgrade protection is just a failsafe to keep people with the new hardware from bricking their device then.
Wonder too what the difference is.
Anyway, can't see any reason why the existing python script wouldn't work for you.
Thanks. I will try and inform in a couple of days.
-
Thanks. I will try and inform in a couple of days.
I would be very interested in your results - I'm leaning towards getting a "low end" SDS2000X scope and *cough* "upgrading" it, over buying a Rigol and doing the same, but I'm leery of splashing that much cash if it turns out not to be upgradeable any more...
-
but I'm leery of splashing that much cash if it turns out not to be upgradeable any more...
You can avoid this by buying the upgrades, step by step.. ;)
(Or wait for the next "all options included" round)
-
but I'm leery of splashing that much cash if it turns out not to be upgradeable any more...
You can avoid this by buying the upgrades, step by step.. ;)
(Or wait for the next "all options included" round)
Awww, you're no fun :)
-
Guys, using telnet I backed up the configuration folders from the scope into a USB stick before trying the hack.
Here you can find the procedure:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg4130797/#msg4130797 (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg4130797/#msg4130797)
-
My SDS2104X+ scope has just come with the firmware version is .
Release notes say that the difference is compatibility with the new hardware revision (04-05).
Does anyone know what is changed with this new hardware revision and if the hack is compatible with this firmware?
I can confirm that the hack works flawlessly with the latest version ( 1.3.9R10 ) :-+
-
Excellent :-+
-
I can confirm that the hack works flawlessly with the latest version ( 1.3.9R10 ) :-+
What is your SCPI answer to?
:syst:board?
-
I can confirm that the hack works flawlessly with the latest version ( 1.3.9R10 ) :-+
What is your SCPI answer to?
:syst:board?
600bps_LIC-V1
Is it same with previous batches?
-
600bps_LIC-V1
Is it same with previous batches?
Correct. LIC-V1 means that you have the "classic" option licenses version.
-
600bps_LIC-V1
After complete hacking, including bandwith to 500Mhz ?
-
600bps_LIC-V1
After complete hacking, including bandwith to 500Mhz ?
I think so because, as I've shown you, Siglent didn't code the thing correctly OR didn't expect anyone with a SDS2k+ to issue the command. So the FW is not prepared with the 2k+ designation for 500MHz.
-
OK, I thought it was because of the missing bandwith upgrade (https://www.eevblog.com/forum/testgear/siglent-sds6000-pro-10-and-12-bit-dso-coming/msg4074496/#msg4074496).
-
OK, I thought it was because of the missing bandwith upgrade (https://www.eevblog.com/forum/testgear/siglent-sds6000-pro-10-and-12-bit-dso-coming/msg4074496/#msg4074496).
:palm: And you thought well. I wrote from memory and was wrong... Let's see if ozkarah has upgraded to 500M and if his response was after upgrade.
-
OK, I thought it was because of the missing bandwith upgrade (https://www.eevblog.com/forum/testgear/siglent-sds6000-pro-10-and-12-bit-dso-coming/msg4074496/#msg4074496).
:palm: And you thought well. I wrote from memory and was wrong... Let's see if ozkarah has upgraded to 500M and if his response was after upgrade.
Yes, I did the bw update in 200->350-->500 MHz order. And the response was after the update?
Could you pls explain what is wrong with the response ?
-
Maybe nothing, I got the response "4CH_500M" from my scope at home, one of the first sds2k+ and completely hacked.
Then I did the SCPI request on one of our brandnew 100Mhz SDS2k+ at work with no hack at all and get the same response like you got.
But that´s tv84´s playground, he will knows it better.
-
Maybe nothing, I got the response "4CH_500M" from my scope at home, one of the first sds2k+ and completely hacked.
Then I did the SCPI request on one of our brandnew 100Mhz SDS2k+ at work with no hack at all and get the same response like you got.
But that´s tv84´s playground, he will knows it better.
Did you do the bw hack using the keygen or removing the bandwidth file?
And FYI: scope model is shown as SDS2504X Plus after the hack.
-
Did you do the bw hack using the keygen or removing the bandwidth file?
It was "so long" time ago, I don´t know it anymore... ;)
But it wasn´t with the license generator, except the (later added)Manchester and Sent decoding options I´ve used the known gen for.
-
Did you do the bw hack using the keygen or removing the bandwidth file?
It was "so long" time ago, I don´t know it anymore... ;)
But it wasn´t with the license generator, except the (later added)Manchester and Sent decoding options I´ve used the known gen for.
That might be the cause of the difference.
I used the keygen for all. And I did the bandwidth upgrade following the 100->200->350->500 MHz path with rebooting after each.
-
Yes, I did the bw update in 200->350-->500 MHz order. And the response was after the update?
Could you pls explain what is wrong with the response ?
Your SCPI response was obtained after you do the BW licensing up to 500MHz?
-
Yes, I did the bw update in 200->350-->500 MHz order. And the response was after the update?
Could you pls explain what is wrong with the response ?
Your SCPI response was obtained after you do the BW licensing up to 500MHz?
Yes
-
Hopefully next year I'll get a 2104Xplus, and if I can still upgrade it (for free), it should be the best scope for the money, I can get, and it should last me for years, as long as the chips last.
-
I just bought the SDS2074X+, the Chinese market is $930, the crack is still valid, the latest firmware version 1.3.9R12
-
I just upgraded to R12 firmware, but when I connect via SCPI and issue :syst:board? my scope locks up, TCP/IP connection is lost, UI frozen and needs a hard power off to restart.
*IDN? works fine, gives Siglent Technologies,SDS2504X Plus,SDS2PDDQ5R2444,5.0.1.3.9R12.
Any thoughts? I am using Keysight Interactive IO for the SCPI commands.
-
I just upgraded to R12 firmware, but when I connect via SCPI and issue :syst:board? my scope locks up, TCP/IP connection is lost, UI frozen and needs a hard power off to restart.
*IDN? works fine, gives Siglent Technologies,SDS2504X Plus,SDS2PDDQ5R2444,5.0.1.3.9R12.
Any thoughts? I am using Keysight Interactive IO for the SCPI commands.
I have the same scope and FW. I get response on both commands without any lock up.
*IDN?:
Siglent Technologies,SDS2504X Plus,SDS2PEEC6Rxxx5,5.3.1.3.9R12
:syst:board?:
600bps_LIC-V1
1- Try using SCPI control interface of scope's web interface.
2- My device's hw version is 04-05 (new hw revision of Siglent) Please check if it is same with yours.
3- You can compare other system information :
- Uboot OS Version: 5.3
- FPGA Verison: 2022-02-08
- CPLD Version: 05
4- In the Utility Menu, "Tek Mode" is off. Please check yours.
-
I just upgraded to R12 firmware, but when I connect via SCPI and issue :syst:board? my scope locks up, TCP/IP connection is lost, UI frozen and needs a hard power off to restart.
*IDN? works fine, gives Siglent Technologies,SDS2504X Plus,SDS2PDDQ5R2444,5.0.1.3.9R12.
Any thoughts? I am using Keysight Interactive IO for the SCPI commands.
I have the same scope and FW. I get response on both commands without any lock up.
*IDN?:
Siglent Technologies,SDS2504X Plus,SDS2PEEC6Rxxx5,5.3.1.3.9R12
:syst:board?:
600bps_LIC-V1
1- Try using SCPI control interface of scope's web interface.
2- My device's hw version is 04-05 (new hw revision of Siglent) Please check if it is same with yours.
3- You can compare other system information :
- Uboot OS Version: 5.3
- FPGA Verison: 2022-02-08
- CPLD Version: 05
4- In the Utility Menu, "Tek Mode" is off. Please check yours.
Mine also locks up. Has done since the command was first published and I was on R6, now on R12
TEK mode off. Command sent through scope web interface.
- Uboot OS Version: 5.0
- FPGA Verison: 2021-07-16
- CPLD Version: 03
- HW: 02-04
-
Hmm.....
The new owner of my sds2k+ reported me, he had a freeze while booting - This I´ve never got before in the 2.5yrs of using the scope.
One of the last things I´ve done was to upgrade the firmware from R6 to R12....
Maybe that was not a good idea.
-
It should be a bug but, just in case, I ask the guys with lock ups to check the file NSP_system_info.xml and see if there is any reference to a "Dynamic Key"?
-
Thanks to everyone who contributed to provide a keygen and also for foolproof instructions how to use it.
Also good to read the info about new firmware. Mine is still running 1.3.7R5 and i wanted to update soon. So reading the changelog the best option might be to update to 1.3.9R6 since the newer ones are mostly for compatibility with new hardware.
-
R6 is a "must" as the FFT bug was fixed with it, the other ones don´t have an effect when the scope got the "old" hardware (as far I could test it before selling my scope).
-
I’ve not had any lock ups on R12 (running for a few weeks now), and on the older hardware.
Only locks on running the :syst:board? command.
No Dynamic Key in NSP file.
-
Hack works.
V1.3.9R12
:syst:board?
600bps_LIC-V1
-
I'm tempted to get an SDS2074X or SDS2104X and upgrade it all the way to 350MHz with all options
Anything specific I need to look out for?
-
I'm tempted to get an SDS2074X or SDS2104X and upgrade it all the way to 350MHz with all options
Anything specific I need to look out for?
Just be sure you order the correct model with the suffix Plus. ;)
Pray do tell where you plan to get the 70 MHz model from as it's not available in the west.
TBH there were great deals on these last year for the MSO HW with MSO and FG license for $219 was hard to beat.
-
Yeah, I saw the 70MHz has been discontinued, shame! But still a bargain for a 100MHz scope that can go up to 350MHz.
-
Yeah, I saw the 70MHz has been discontinued, shame! But still a bargain for a 100MHz scope that can go up to 350MHz.
It's still a current model....in the east !
IIRC the 70 MHz model has never been available in the west and the only model listed as discontinued is the 2ch SDS2102X Plus.
Actually these 2kX Plus have a 500 MHz BW option however it's SW limited to just 2 channels so if you planned on liberating it so, and most do, consider getting a couple of fixed 10x sensing 500 MHz probes.
You only need 2 as if you enable a 3rd channel BW limiters kick in at 350 MHz.
The 500 MHz BW has been confirmed by a few members to 570 MHz.
-
Has anybody had any issues with firmwares V1.3.9R12 or V1.3.9R10?
-
Has anybody had any issues with firmwares V1.3.9R12 or V1.3.9R10?
There might be some infos here:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-bugs-missing-features-feature-requests/ (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-bugs-missing-features-feature-requests/)
-
Hi
Any ideas if the bandwidth hack up to 500 MHz is still applicable to SDS2104X Plus (100 MHz unit) on the latest units being shipped right now. Wondering if the newer units have some new hardware revision or hardware + firmware revision to prevent that?
Thank you
-
Hi
Any ideas if the bandwidth hack up to 500 MHz is still applicable to SDS2104X Plus (100 MHz unit) on the latest units being shipped right now. Wondering if the newer units have some new hardware revision or hardware + firmware revision to prevent that?
Thank you
Well it's not really a hack as valid BW license upgrade keys are being installed. Stop that and the BW upgrades that you could otherwise buy might not work and therefore ruin an advertised BW upgrade process which Siglent has added to nearly all of their later DSO ranges.
If you've been lurking here a while you may have noticed some recent flagship models are now using a different licensing Python Hashkey as the clever people here don't appear to sit on their hands for very long.
-
Thank you, and if I understood correctly, the already known hash key is still valid for recently manufactured SDS2000X+ units...?
Well it's not really a hack as valid BW license upgrade keys are being installed. Stop that and the BW upgrades that you could otherwise buy might not work and therefore ruin an advertised BW upgrade process which Siglent has added to nearly all of their later DSO ranges.
If you've been lurking here a while you may have noticed some recent flagship models are now using a different licensing Python Hashkey as the clever people here don't appear to sit on their hands for very long.
-
Thank you, and if I understood correctly, the already known hash key is still valid for recently manufactured SDS2000X+ units...?
Well it's not really a hack as valid BW license upgrade keys are being installed. Stop that and the BW upgrades that you could otherwise buy might not work and therefore ruin an advertised BW upgrade process which Siglent has added to nearly all of their later DSO ranges.
If you've been lurking here a while you may have noticed some recent flagship models are now using a different licensing Python Hashkey as the clever people here don't appear to sit on their hands for very long.
Last I checked a few weeks ago it still generated the same as an official license.
Even if it didn't the experts here would find another one within a week would be my guess.
The Toy Wonder is a very clever chap. ;)
-
Last I checked a few weeks ago it still generated the same as an official license.
Even if it didn't the experts here would find another one within a week would be my guess.
The Toy Wonder is a very clever chap. ;)
Thank you :-+
-
Last I checked a few weeks ago it still generated the same as an official license.
Even if it didn't the experts here would find another one within a week would be my guess.
The Toy Wonder is a very clever chap. ;)
I was interested int his as well, seeing that the new HW revision (04-xx) gets LXi in the latest FW...
-
hi ,
What is reason to have license for Siglent SPL2016 PLUS 16 Channel logic probe , if you can't buy the probe separately ?
Or can you buy separately the logic probe ? I can't find nowhere . Maybe some 3rd party compatible ?
-
hi ,
What is reason to have license for Siglent SPL2016 PLUS 16 Channel logic probe , if you can't buy the probe separately ?
Or can you buy separately the logic probe ? I can't find nowhere . Maybe some 3rd party compatible ?
SPL2016 can be bought without any problems, e.g. in Batronix, it is also available from a Polish distributor. Although it is not cheap (335 euro netto, 405,35 euro with VAT 21%), unfortunately. There is also an amateur project of making such a probe on the forum.
-
hi ,
What is reason to have license for Siglent SPL2016 PLUS 16 Channel logic probe , if you can't buy the probe separately ?
Or can you buy separately the logic probe ? I can't find nowhere . Maybe some 3rd party compatible ?
They are.
Some LeCroy, Tek and Rigol MSO's use the same probe and sometimes you can find them surplus on eBay.
Obviously the Pt#'s are different but some time spent surfing the net can find them.
The DIY probe thread is here:
https://www.eevblog.com/forum/testgear/diy-logic-analyzer-probe-and-pods-for-siglent-scopes/ (https://www.eevblog.com/forum/testgear/diy-logic-analyzer-probe-and-pods-for-siglent-scopes/)
Youtuber Defpom made his own style here:
https://www.youtube.com/watch?v=hL_YPqaD9Pg (https://www.youtube.com/watch?v=hL_YPqaD9Pg)
-
You guys are amazing point me newcomer to right direction , I will go with a DIY probe + lic . key here and have fun !
-
I've seen negative comments about the SDS2104X+ logic probes. I'm not clear if that is because there are considered poor quality, or too expensive. There is a bundle being offered right now (at least in the UK) that makes the logic probe cheaper. Can anyone comment on the quality versus value for money issue?
-
I've seen negative comments about the SDS2104X+ logic probes. I'm not clear if that is because there are considered poor quality, or too expensive. There is a bundle being offered right now (at least in the UK) that makes the logic probe cheaper. Can anyone comment on the quality versus value for money issue?
I don't know what negative comments.. SPL2016 are very good quality, and bundle is great deal. Usually they are more expensive because you have to pay for both probes and MSO license separately.
-
hi ,
What is reason to have license for Siglent SPL2016 PLUS 16 Channel logic probe , if you can't buy the probe separately ?
Or can you buy separately the logic probe ? I can't find nowhere . Maybe some 3rd party compatible ?
Of course, you can buy SPL2016 separately. Just SPL2016 without license (normal price EUR 355,- VAT 0)
Example if your probe is damaged or loosed in travel or destroyed accidentally way or other no need buy licence again. It is permanently in scope. So you can buy just only new SPL2016 probe.
And more if you need only new very good quality original clips you can then buy clips set. SPL-C1 (normal price EUR 79,- VAT0)
And even more: if workshop have 10 scopes and want all have MSO license but all do not all time/same time need probe, just buy ten licenses but only example two probe set and then every scope user can take probe just only when need occasionally and after use return it to the tool storage of workshop. License SDS2000XP-16LA without probe normal price is EUR 155,- VAT0.
Or vice versa, if need test many separate objects and freguently swap between these but connecting probes take too much time including also possible mistakes... you can buy 10 probe for one scope with one license and probes can be already connected to circuits under work and then just need connect this probe to scope what circuit need look. Much faster and less errors if connecting probe to DUT circuit is laborious (time is money!)
Does separate pricing still feel strange?
Of course, now this bundle offer is different case. One probe+licence together for one new oscilloscope with special price.
Btw, this SPL2016 is really good quality and example ribbon cables consist of separate coaxial cables (specially for keep fast edges cross talk low)
-
Although it is not the right thread for it(hacking):
I would love it if "early adpoters" like me could also enjoy a promo offer like this... ;)
As a reward for buying so early, you can always pay full price for every accessory...
-
I've seen negative comments about the SDS2104X+ logic probes. I'm not clear if that is because there are considered poor quality, or too expensive. There is a bundle being offered right now (at least in the UK) that makes the logic probe cheaper. Can anyone comment on the quality versus value for money issue?
Normal SLA2016 pricing is outrageous but the promo bundle with a new scope, SLA2016, MSO and FG option licenses for $ 220 is a killer deal.
Quality grabbers and the twin 8ch leads, well you just can't know how nice they are until you fondle a set.
Just stocked up on a few .........
-
Normal SLA2016 pricing is outrageous....
Really? If look markets it is more like el cheapo (except quality)
8 channel cheap LA probe, N2755A from Keysight:
https://www.datatec.eu/en/keysight-n2755a-mso-logik-kabel (https://www.datatec.eu/en/keysight-n2755a-mso-logik-kabel)
Or from Tektronix P6316 16 channel:
https://www.distrelec.nl/en/mso-probe-16-channel-for-mso3000-40v-tektronix-p6316/p/17623517?track=true&no-cache=true&marketingPopup=false (https://www.distrelec.nl/en/mso-probe-16-channel-for-mso3000-40v-tektronix-p6316/p/17623517?track=true&no-cache=true&marketingPopup=false)
-
Normal SLA2016 pricing is outrageous....
Really? If look markets it is more like el cheapo (except quality)
8 channel cheap LA probe, N2755A from Keysight:
https://www.datatec.eu/en/keysight-n2755a-mso-logik-kabel (https://www.datatec.eu/en/keysight-n2755a-mso-logik-kabel)
Or from Tektronix P6316 16 channel:
https://www.distrelec.nl/en/mso-probe-16-channel-for-mso3000-40v-tektronix-p6316/p/17623517?track=true&no-cache=true&marketingPopup=false (https://www.distrelec.nl/en/mso-probe-16-channel-for-mso3000-40v-tektronix-p6316/p/17623517?track=true&no-cache=true&marketingPopup=false)
Yes really.
It's a 3rd party device with little reason to be so expensive at normal pricing.
https://siglentna.com/product/spl2016-16-channel-logic-probe-for-mso-option-sds2000x-oscilloscope-family/ (https://siglentna.com/product/spl2016-16-channel-logic-probe-for-mso-option-sds2000x-oscilloscope-family/)
Whereas I have no problem with the cost of MSO option pricing, after all there must be some ROI for development costs.
https://siglentna.com/product/16-digital-channelssoftware/ (https://siglentna.com/product/16-digital-channelssoftware/)
So lets look at what we might instead buy for the $379 SLA2016 price......maybe a nice little 200 MHz SDS1202X-E DSO where the development and IP is certainly Siglent based and if we look at each of the HW, SDS1202X-E and SLA2016, please tell me which is the best value for money.
https://siglentna.com/product/sds1202x-e/ (https://siglentna.com/product/sds1202x-e/)
Instead, SLA2016, MSO and FG option licenses for $ 220 on promotion is incredible value.
-
Weren't these supposed to go on sale this week?
-
Weren't these supposed to go on sale this week?
Many models have.
Here's the info for the SDS2000X Plus range:
https://int.siglent.com/info/detail-63.html
-
Weren't these supposed to go on sale this week?
Many models have.
Here's the info for the SDS2000X Plus range:
https://int.siglent.com/info/detail-63.html
Yes, I see even in Canada prices have come down! This is worth considering.
-
Weren't these supposed to go on sale this week?
Many models have.
Here's the info for the SDS2000X Plus range:
https://int.siglent.com/info/detail-63.html
Yes, I see even in Canada prices have come down! This is worth considering.
You have 8 weeks !
More are here:
https://siglentna.com/news-and-events/siglent-promotions/
-
Pulled the trigger 5 minutes a go.... :scared:
-
WIFI isn't mentioned in the SDS2000X Plus datasheet. Has that capability been added in firmware updates or been enabled through a hack?
-
WIFI isn't mentioned in the SDS2000X Plus datasheet. Has that capability been added in firmware updates or been enabled through a hack?
AFAIK there is no WIFI hardware on board.
I use a tp-link wifi-router:
https://www.tp-link.com/en/home-networking/wifi-router/tl-wr802n/ (https://www.tp-link.com/en/home-networking/wifi-router/tl-wr802n/)
which is working fine.
-
Oh, I meant if it could work with USB Wifi like the SDS1104X-E (ie., using a TP-Link TL-WN725N (https://www.amazon.com/dp/B008IFXQFU))
-
Scope came 15 minutes ago and is now a fully decked SDS2504X+.
Now to get to work...
-
Oh, I meant if it could work with USB Wifi like the SDS1104X-E (ie., using a TP-Link TL-WN725N (https://www.amazon.com/dp/B008IFXQFU))
No, it is Ethernet or USB .. no WIFI. Just tried and it does not even recognize the WIFI TP-Link dongle.
-
I'm SERIOUSLY considering to "Hit the buy button"
https://www.batronix.com/shop/oscilloscopes/Siglent-SDS2104X-plus.html (https://www.batronix.com/shop/oscilloscopes/Siglent-SDS2104X-plus.html)
But i need it to become 350MHz , or prefreably 500MHz
Can anyone confirm that "Recent scopes" accept the "Keygen" ?
/Bingo
-
I'm SERIOUSLY considering to "Hit the buy button"
https://www.batronix.com/shop/oscilloscopes/Siglent-SDS2104X-plus.html (https://www.batronix.com/shop/oscilloscopes/Siglent-SDS2104X-plus.html)
But i need it to become 350MHz , or prefreably 500MHz
Can anyone confirm that "Recent scopes" accept the "Keygen" ?
/Bingo
Mine did last week.
-
Can anyone confirm that "Recent scopes" accept the "Keygen" ?
Ordered last week from Batronix, no problem.
Just started to create .lic files, had not yet the network configured and the touchscreen was getting annoying to enter the codes.
-
Can anyone confirm that "Recent scopes" accept the "Keygen" ?
Ordered last week from Batronix, no problem.
Just started to create .lic files, had not yet the network configured and the touchscreen was getting annoying to enter the codes.
So so much easier within the scopes webserver SCPI command panel.
SCPI command/license and Copy/Paste. Done !
If you have the scope option/license page open you can watch each one in turn get converted to Permanent.
Even new before dispatch we do it like this and can easy clear our IP from the scope with the Secure Erase.
-
I'm SERIOUSLY considering to "Hit the buy button"
https://www.batronix.com/shop/oscilloscopes/Siglent-SDS2104X-plus.html (https://www.batronix.com/shop/oscilloscopes/Siglent-SDS2104X-plus.html)
But i need it to become 350MHz , or prefreably 500MHz
Can anyone confirm that "Recent scopes" accept the "Keygen" ?
/Bingo
Well i did hit buy @Batronix - €1199 incl. DK VAT (extaa 6%) DK is 25 %
Hope the "Upgrade goes well" ...
/Bingo
-
Congrats! :-+
-
Thanx to the nice users of this board. :-+
I now have a "Fully loaded" - SDS2504X Plus 8)
I didn't send/enable Opt. WIFI. Don't think it would work anyway, and wouldn't use it.
What is Opt. MAX ??
I don't see it on the options page in the scope, or ?
/Bingo
-
I didn't send/enable Opt. WIFI. Don't think it would work anyway, and wouldn't use it.
SDS2000X Plus doesn't support WiFi.
-
Just post new info.
Got a sds2074X Plus last week, firmware version is 1.3.5R5.
Keygen is works too.
Thanks guys.
-
Here are the results of using an ADF4350 to look at the BW of an "improved" SDS2104XP. The 50 ohm termination is enabled on the scope and I'm using a 6" coax to connect the FG to the scope
Please have a look at the shots and see if my assumptions are more or less correct.
My assumptions here are:
1) Max amplitude = 550mV (see the shot @400MHz)
2) -3dB = .707*550 = 389mV
3) Due to the square wave from the ADF4350, these results need to be taken as an approximation.
I was tempted to take 500mV as the maximum and put the increase in amplitude @400MHz as overshoot, however that leads to a BW in excess of 680MHz!
-
@BillyO
IMHO i find your measurement method (display) a bit confusing, might be my lack of understanding.
Btw: don't you have a strange "dip" @200MHz ?
I tested mine with an Agilent ESG (locked to a Tbolt) , it is set to output ~100mV PP (~36mV RMS) at 100MHz , and enabled a "Basic screen readout"
Then i just dialed in the other frequencies i wanted to test , and found the -3dB just below 600MHz.
My SMA adapters are in the summerhouse, so i had to use a RG58 cable with a N-BNC on the ESG.
I was quite impressed to see the Scope Freq counter to be 100% spot on, all the way to 600MHz
The "Scope readout" freq, was deviating, but the one in the top was "spot on"
/Bingo
-
@BillyO
IMHO i find your measurement method (display) a bit confusing, might be my lack of understanding.
Btw: don't you have a strange "dip" @200MHz ?
I tested mine with an Agilent ESG (locked to a Tbolt) , it is set to output ~100mV PP (~36mV RMS) at 100MHz , and enabled a "Basic screen readout"
Then i just dialed in the other frequencies i wanted to test , and found the 3dB just below 600MHz.
My SMA adapters are in the summerhouse, so i had to use a RG58 cable with a N-BNC on the ESG.
I was quite impressed to see the Scope Freq counter to be 100% spot on, all the way to 600MHz
The "Scope readout" freq, was deviating, but the one in the top was "spot on"
/Bingo
Nice measurements..
Frequency "on top " is actual hardware frequency counter in the scope. Since these scopes have decent clock source they are quite accurate.
Frequency measurements from measurements menu are based on sampled data and are less accurate. That is normal. If you enable statistics, and play with timebase you can get averaged values that are closer.
-
@BillyO
IMHO i find your measurement method (display) a bit confusing, might be my lack of understanding.
I had the stats turned on to get averaging. The "Mean" for both amplitude and Tr. I just ran each measurement for a few hundred counts until the Mean stabilized.
Btw: don't you have a strange "dip" @200MHz ?
Something to do with the square wave and overshoot is my guess. As the signal becomes more sinusoidal it begins behaving better. Later I was able to get some software for the ADF4350 that allowed me to run it at as low as 35MHz so I could get a better reading of the actual amplitude. It is 0.505V so the end point @ 0.36V should be valid. This all needs to be verified with a sine wave generator. I don't have one that will go up this high, but I know someone that does. I just need to arrange to bring it over. Maybe after Christmas.
The timebase in my ADF4350 is just an everyday SMD oscillator can, so the frequency was a tad off (~5ppm). I'm sure the Siglent timebase is the better of the two.
-
There are reports from knowing users early after X Plus release full BW is from 580-620MHz , why do we need confirm this again ? :-//
-
There are reports from knowing users early after X Plus release full BW is from 580-620MHz , why do we need confirm this again ? :-//
Because when I first did the "improvement" using the MSCP MCBD command to install the 500MHz license out of the box the best I could get (using a sine wave generator) was 266MHz and there was quite a bit of distortion on the rising edge of the signal in the form of a much slower rise time on the 2nd half of the rising edge. The model ID was changed to SDS2504X Plus but it was NOT running at 500MHz.
I then used the MSCP MCBD command to put it back to 100MHz and then installed the licenses 200 -> 350 -> 500 using the UI and now I'm getting better than 600MHz.
I think the 500MHz license makes certain adjustments but not all of them. It requires the scope to be already at 350MHz.
So .. my plan is to get in front of the SW generator again, put it back to 100MHz, do the direct to 500MHz MSCP MCBD command and see what I get. If it's the same as last time, then I'll take a screen shot. Then I'll do the 100 -> 200 -> 350 -> 500 again and run a series and let everyone know the results.
Maybe folks that are doing the 500MHz directly with the MSCP MCBD command are not getting what they think. I know bingo600 did it through the UI .. he's getting good results and when I did it through the UI I got better results.
Besides, this is fun.
-
Besides, this is fun.
:-+
Just use MCBD instead of MSCP. Should provide even more BW... :-DD
-
Right! :palm:
-
So so much easier within the scopes webserver SCPI command panel.
SCPI command/license and Copy/Paste. Done !
That's a good idea. Would you please provide the SCPI license command? I cannot find any trace of it in the SCPI programming manual...
Thanks!
-
That's a good idea. Would you please provide the SCPI license command? I cannot find any trace of it in the SCPI programming manual...
Thanks!
It's: MCBD [license code]
I would at least do the 350MHz license before doing the 500MHz license. When I tried going directly to the 500MHz code I did not end up with a 500MHz scope. I ended up with a 266MHz scope that had an annoying distortion on the top have of the signal. It only takes about 10 seconds for each command to be entered, so I'd suggest you do the 200MHz, then the 350MHz then the 500MHz as it's possible each license tweaks the BW capability in a different way.
-
That's a good idea. Would you please provide the SCPI license command? I cannot find any trace of it in the SCPI programming manual...
Thanks!
It's: MCBD [license code]
I would at least do the 350MHz license before doing the 500MHz license. When I tried going directly to the 500MHz code I did not end up with a 500MHz scope. I ended up with a 266MHz scope that had an annoying distortion on the top have of the signal. It only takes about 10 seconds for each command to be entered, so I'd suggest you do the 200MHz, then the 350MHz then the 500MHz as it's possible each license tweaks the BW capability in a different way.
Thanks! So, just MCBD license?
No other commands to confirm or whatever?
Another quick question:
Is there some firware, between 1.3.9 and 1.5.2r1 that *solves* the bugs BUT *retains* the telnet server? [EDIT: it seems that's not the case, at least not on the official support site..]
Thanks!
-
And yet another question. These are the default options for the keygen
'25M', '40M', '50M', '60M', '70M', '100M', '150M', '200M', '250M', '300M', '350M', '500M', '750M', '1000M', 'MAX', 'AWG', 'WIFI', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA'
Some of them are clearly invalid, and probably made for SDS5K or 1000X-E/U (e.g. wifi, 1000M). Apart from that, is there something else which is unlockable but not included by default?
Thanks.
-
No other commands to confirm or whatever?
The scope will respond if the command was successful. You can also check that the model ID changes as expected by issuing a *IDN? command or looking at the "Home" page.
You should re-start the scope after issuing each command.
-
'200M', '350M', '500M', 'MAX', 'AWG', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA'
These are the valid codes for the SDS2004XP series scopes. I have no idea what MAX does, but the scope accepts it.
Of course you can go back to 100MHz bandwidth by issuing the "100" license key. You might want to do that if you are returning the scope for warranty work. :-//
When I did my other options (other than BW), I entered them through the GUI. Can't remember why now, except to try that way out. It worked too.
-
'200M', '350M', '500M', 'MAX', 'AWG', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA'
These are the valid codes for the SDS2004XP series scopes. I have no idea what MAX does, but the scope accepts it.
You missed 100M. :P
-
You missed 100M. :P
Fixed that.
-
Thanks for the assistance.
Commands sent to the scope via SCPI, strange results..
Sent 350M, accepted, rebooted, sent 500M, accepted, rebooted.
Now it reports Siglent Technologies, SDS2504X Plus
Sent AWG, accepted, rebooted, it works. This was the last one it accepted by SCPI.
For MSO and all the decoding options, it doesn't accept them via SCPI. It does accept them, though, if I manually enter it (did that for MSO function and one decoding...).
Tell me.. Where can I find a more complete SCPI reference? The commands you told me worked, but they are not into the programming manual... Thanks.
-
Mh, I think MAX is Manchester.
-
For MSO and AWG I have authentic Siglent codes, since I bought the logic probe with the special deal.
However, it's worth noting that:
1. They are *different* from the ones generated by the keygen.
2. I used the ones by the keygen, and the scope accepted it.
How can I check if the scope can really display a high-bw signal (say close to 500 MHz)? My discrete AWG only gets to 30 MHz, amd the integrated one to 50 MHz.
-
Mh, I think MAX is Manchester.
It is not.
Thanks for the assistance.
Commands sent to the scope via SCPI, strange results..
Tell me.. Where can I find a more complete SCPI reference? The commands you told me worked, but they are not into the programming manual... Thanks.
Wrong licenses or an errors in your commands, just a space in the wrong place will break it !
There is NO need for system reboots between installation of licenses.
-
For MSO and AWG I have authentic Siglent codes, since I bought the logic probe with the special deal.
However, it's worth noting that:
1. They are *different* from the ones generated by the keygen.
2. I used the ones by the keygen, and the scope accepted it.
How can I check if the scope can really display a high-bw signal (say close to 500 MHz)? My discrete AWG only gets to 30 MHz, amd the integrated one to 50 MHz.
Warning, warning, Houston we have a problem !
Too much hurry and not enough care.
-
'200M', '350M', '500M', 'MAX', 'AWG', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA'
These are the valid codes for the SDS2004XP series scopes. I have no idea what MAX does, but the scope accepts it.
You missed 100M. :P
And SENT and Manch too !
Optional protocols:
I2S, FlexRay, 1553B, CANFD, SENT, Manch
It would seem the script in use is some old variant from before the additional Decodes were added in a firmware release.
-
There is NO need for system reboots between installation of licenses.
Good to know for the future. When I entered the other option codes through the GUI it asked to re-start after each one. So I complied.. :-//
-
And SENT and Manch too !
Optional protocols:
I2S, FlexRay, 1553B, CANFD, SENT, Manch
It would seem the script in use is some old variant from before the additional Decodes were added in a firmware release.
My Bad. My script has them but I was just choosing from the list presented by balnazzar.
-
And SENT and Manch too !
Optional protocols:
I2S, FlexRay, 1553B, CANFD, SENT, Manch
It would seem the script in use is some old variant from before the additional Decodes were added in a firmware release.
My Bad. My script has them but I was just choosing from the list presented by balnazzar.
Where can I find such a script? I'm using the one originally linked.
-
How can I check if the scope can really display a high-bw signal (say close to 500 MHz)? My discrete AWG only gets to 30 MHz, amd the integrated one to 50 MHz.
That's the question. I'm in the process now. The best way would be find a sinewave generator that will go flat out to 1GHz then have a look at the response. Another way, not as precise but a good indicator, is to find a fast risetime pulse generator and see what the minimum rise time on the scope is. For this scope you will need a pulse with a rise time of better than 500ps. I have a ~ 30ps pulser on the way (delayed due to The Royal Mail being on strike) and have access to a 1GHz generator. So, over the next little while I'll be doing some testing .. just for fun.
-
Where can I find such a script? I'm using the one originally linked.
Here:
import hashlib
SCOPEID = 'xxxxxxxxxxxxxxxx'
Model = 'SDS2000X+'
bwopt = ('25M', '40M', '50M', '60M', '70M', '100M', '150M', '200M', '250M', '300M', '350M', '500M', '750M', '1000M', 'MAX', 'AWG', 'WIFI', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA', 'MANC', 'SENT')
hashkey = '5zao9lyua01pp7hjzm3orcq90mds63z6zi5kv7vmv3ih981vlwn06txnjdtas3u2wa8msx61i12ueh14t7kqwsfskg032nhyuy1d9vv2wm925rd18kih9xhkyilobbgy'
def gen(x):
h = hashlib.md5((
hashkey +
(Model+'\n').ljust(32, '\x00') +
opt.ljust(5, '\x00') +
2*((SCOPEID + '\n').ljust(32, '\x00')) +
'\x00'*16).encode('ascii')
).digest()
key = ''
for b in h:
if (b <= 0x2F or b > 0x39) and (b <= 0x60 or b > 0x7A):
m = b % 0x24
b = m + (0x57 if m > 9 else 0x30)
if b == 0x30: b = 0x32
if b == 0x31: b = 0x33
if b == 0x6c: b = 0x6d
if b == 0x6f: b = 0x70
key += chr(b)
return key.upper()
for opt in bwopt:
print('{:5} {}'.format(opt, gen(SCOPEID)))
-
There is NO need for system reboots between installation of licenses.
Good to know for the future. When I entered the other option codes through the GUI it asked to re-start after each one. So I complied.. :-//
Fair enough.
Put yourself in my position when installing licenses before shipping an instrument to customers.
Many instruments have boot counters so for each license install add another boot then any additional if FW updates are needed and very quickly you can have 10 boots on the boot counter.....does this still look like a new instrument when the customer receives it ?
Then there also the time to need to wait between boots ............. no thank you so we develop time saving methods to do this stuff or instead as some dealers do, throw it all in the box and let the customer sort it.
Isn't that a wonderful example of quality dealer support ? :horse:
Where can I find such a script? I'm using the one originally linked.
Here:.............
As you already know this script or variations of it can also improve other instruments so we look for the most complete version. ;)
balnazzar had it all in her hand to check official licensing against script results but never used the sanity check staring her in the face......this is how I first discovered proper script generated licenses were accurate. ;)
-
Isn't that a wonderful example of quality dealer support ? :horse:
:-+
-
balnazzar had it all in her hand to check official licensing against script results but never used the sanity check staring her in the face......this is how I first discovered proper script generated licenses were accurate. ;)
I am a male human being, just for the sake of clarity ;D
How not? I posted above that the licenses are *different*, but the scope accepts the ones generated by the keygen nonetheless...!
Probably there are more than just 1 valid hash.
I can confirm, however, that the scope accepted the licenses via SCPI only for the bw limits and the awg. All the other had to be entered manually.
It's strange, I know. But had it be a mess by my part, it wouldn't have accepted bw and awg... And it's very hard to make errors when you have just to enter MCBD license...
-
ADDENDUM: The license codes generated by the updated script are the same as the ones before, except for the presence of MANC and SENT. I still don't know what MAX is, given that it's evidently not Manchester.
Of course, the MSO and AWG codes provided by the new script, being identical to the ones by the old script, are different from the genuine ones provided by Siglent.
-
balnazzar had it all in her hand to check official licensing against script results but never used the sanity check staring her in the face......this is how I first discovered proper script generated licenses were accurate. ;)
I am a male human being, just for the sake of clarity ;D
Please accept my apologies ......your christian name is normally female where we are. :-[
ADDENDUM: The license codes generated by the updated script are the same as the ones before, except for the presence of MANC and SENT. I still don't know what MAX is, given that it's evidently not Manchester.
Of course, the MSO and AWG codes provided by the new script, being identical to the ones by the old script, are different from the genuine ones provided by Siglent.
This is of concern. :-//
Did you dealer supply the actual license codes or a form with authorization code to generate the licenses at the Siglent license site ?
-
balnazzar had it all in her hand to check official licensing against script results but never used the sanity check staring her in the face......this is how I first discovered proper script generated licenses were accurate. ;)
I am a male human being, just for the sake of clarity ;D
Please accept my apologies ......your christian name is normally female where we are. :-[
ADDENDUM: The license codes generated by the updated script are the same as the ones before, except for the presence of MANC and SENT. I still don't know what MAX is, given that it's evidently not Manchester.
Of course, the MSO and AWG codes provided by the new script, being identical to the ones by the old script, are different from the genuine ones provided by Siglent.
This is of concern. :-//
Did you dealer supply the actual license codes or a form with authorization code to generate the licenses at the Siglent license site ?
No need to apologize, it was actually funny :)
I got two PDF certificates, sent via e-mail by Batterfly, with a big Siglent logo as well as the codes on them, both as barcode and as alphanumeric string.
-
I got two PDF certificates, sent via e-mail by Batterfly, with a big Siglent logo as well as the codes on them, both as barcode and as alphanumeric string.
One for each option is standard.
With install instructions ?
The PDF license we get has alphanumeric and barcodes on it too but must be first redeemed at the Siglent license generation site where then you can chose to download another PDF with the actual option license code for the prescribed instrument (model and SN#) that we can Copy/Paste from and/or print and include in the box when we dispatch.
Maybe you tried to install the redeem code ?
We install purchased options so the instrument is right and ready for work !
-
I got two PDF certificates, sent via e-mail by Batterfly, with a big Siglent logo as well as the codes on them, both as barcode and as alphanumeric string.
One for each option is standard.
With install instructions ?
The PDF license we get has alphanumeric and barcodes on it too but must be first redeemed at the Siglent license generation site where then you can chose to download another PDF with the actual option license code for the prescribed instrument (model and SN#) that we can Copy/Paste from and/or print and include in the box when we dispatch.
Maybe you tried to install the redeem code ?
We install purchased options so the instrument is right and ready for work !
You are right. My bad: I didn't bother reading the whole babbling.. I just eyed the code to compare them with the ones generated by the keygen! |O ^-^
It says:
Thanks for your purchase. The option card info is below. With this, go to the URL below to get the option key and the
installation instructions.
URL: http://service.siglenteu.com/easyweb (http://service.siglenteu.com/easyweb)
Et cetera...
-
:-DD
Trap for young players. :-X
Now go there are generate the official licenses and check they match what you installed.
-
Hello all, what is the status of the current BW hack for the 100MHZ 4 channel model?
Im debating this vs the Rigol 5000 series.
-
Hello all, what is the status of the current BW hack for the 100MHZ 4 channel model?
Welcome to the forum.
Quite simple with the Python script actually but a correction to your thoughts as SDS2104X Plus while badged as 100 MHz is actually much closer to 200 MHz as our BW tests indicated it was actually -3dB at ~185 MHz.
-
Right I see and that's without the hack?
What about after adding the 350MHz BW to the 100MHz model specifically.
-
Right I see and that's without the hack?
What about after adding the 350MHz BW to the 100MHz model specifically.
Why stop at that ?
These are a 500 MHz design and opening all the taps gets you to ~600 MHz but only 350 MHz with all channels active. Siglent added a channel management system so when a 3rd channel is enabled a BW filter is engaged to restrict system BW to 350 MHz to restrict aliasing artifacts.
Do some more reading here and in the SDS2000X Plus thread. ;)
-
Should the code returned from the "MCBD?" command be the same as that generated by the script for option '100M'? I have an SDS2104X Plus purchased in a promotion with decoding. Updated to 1.5.2R2. I'm waiting for the decode option codes to email me. I wanted to check if the ones generated by the script work but they are incorrect (entered via 'software options'). Is it possible that something is changed in this firmware version?
-
Should the code returned from the "MCBD?" command be the same as that generated by the script for option '100M'?
It must.
-
And if they are different? How else to check it?
EDIT:
I checked. I confused the ID with the SN ::) Now it's correct.
-
And if they are different? How else to check it?
In logic terms, if they are different, then you got an error in your code generation.
-
Hello and have a nice day.
I bought the SDS2102X-Plus.
thanks.
Greetings from me, Andy
-
Hello and have a nice day.
I bought the SDS2102X-Plus.
thanks.
Greetings from me, Andy
Nice!
I thought they were discontinued. Did you buy it used?
-
No, I bought it new.
I didn't manage the extension at first, but then I managed it.
According to the options, I only have the 350MHz option.
Does this mean that the SDS2102X-Plus cannot be expanded to 200 and 500MHz?
Greetings from me, Andy
-
Hello and have a nice day.
I bought the SDS2102X-Plus.
thanks.
Greetings from me, Andy
Nice!
I thought they were discontinued. Did you buy it used?
Still available in the EU:
https://www.siglenteu.com/digital-oscilloscopes/sds2000xp/ (https://www.siglenteu.com/digital-oscilloscopes/sds2000xp/)
-
According to the options, I only have the 350MHz option.
Does this mean that the SDS2102X-Plus cannot be expanded to 200 and 500MHz?
Welcome to the forum.
While these BW options don't officially exist it doesn't mean they won't work. Have you tried them ?
Some report the 500 MHz license can only be applied after the 350 MHz one has been.
2ch SDS2000X Plus are not overly popular and the only one that comes to mind that has one is member mawyatt and you might find mention or screenshots from his in the SDS2000C Plus thread or in one of his posts.
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/ (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/)
-
We have a SDS2104X+ and 2102X+. Both "enhanced" and have measured BWs of over 500MHz, the 2102X+ shows as SDS2352X+ tho, while the SDS2104X+ shows as a SDS2504X+.
@Andy.
These SDS2102X+ DSOs have the 10 bit mode which limits the BW to 100MHz, for maximum BW make sure you have the Max BW set for the Channel and are using 8 bit mode :-+
Best,
-
Hi,
I feel misunderstood. :)
After I made the only bandwidth option (350), no other BW option is now available.
The device is now recognized as SDS 2104X Plus, that can't be.
(http://)
Greetings from me, Andy
-
Hi,
I feel misunderstood. :)
After I made the only bandwidth option (350), no other BW option is now available.
The device is now recognized as SDS 2104X Plus, that can't be.
The Sys info page shows the new model # after a successful hack and the Options info page displays temp and permanent option status.
AFAIK you only have FG option permanent at this time......you have some remaining work to do. :)
-
How can I increase the bandwidth to 500 if there is no option for it?
-
How can I increase the bandwidth to 500 if there is no option for it?
Read what mawyatt said.
-
According to the options, I only have the 350MHz option.
Does this mean that the SDS2102X-Plus cannot be expanded to 200 and 500MHz?
Hi,
The "steps" between the (official) bandwith-maximum are not mentioned in the options table.
What the 500Mhz option oncerns, you´ll have the 500Mhz only on 2 channels, one of each ADC.
Enabling the second channel of the same ADC reduces the bandwith automatically back to 350Mhz.
Following this logic only one channel could be used on a 2-ch scope.
Maybe this is a reason why the 2-ch do not have the "official" 500Mhz option avaible.
-
How can I increase the bandwidth to 500 if there is no option for it?
Via SCPI command:
MCBD <BW_code>
-
Where do I enter this? I have no idea.
-
Where do I enter this? I have no idea.
Through the web interface.
-
All right. Now I have entered the 500 Mhz command.Do I see the bandwidth expansion somewhere?
-
All right. Now I have entered the 500 Mhz command.Do I see the bandwidth expansion somewhere?
Utility/Sys info
-
All right.
All that remains for me is to say thank you. :)
For those who also have difficulties with SCPI.
Enter the command and code only separated by spaces, without parentheses, etc.
MCBD xxxxxxxxxxxxxxxx
Have a great week, Andy
-
That went unexpectedly silky smooth compared to upgrading the SSA3021X Plus, i love it ;D Another happy Siglent customer. Thanks to anyone involved in making this possible. :-+
Now i just need to find a reason to buy a SDG6022X also...
-
Which affordable 500 MHz (or higher?) passive probes are recommended for the scope?
-
Affordable is relative but is generally never associated with the words "500MHz (or higher?) passive probes". :-DD
I got a couple of used and (almost) complete Tek P-6139A probes that work well from a seller that I found on eBay. They generally (for the almost complete ones tested an working) run from $150 to $200 each. I ended up getting mine pretty much thrown in on a more comprehensive deal. :-+
I also got a pair of new no-name P-6139A probes that work fairly well for about $41 each off of Amazon. Now, however, they have gone through the roof @ more than $57. https://www.amazon.ca/gp/product/B08P3N9VYG (https://www.amazon.ca/gp/product/B08P3N9VYG)
Just a little update. If you wanted the current model of the Tek P-6139 (the B model) - well .. 4 of them will cost a bit more than twice what your scope cost.
All considered the Siglent SP3050A probes are pretty reasonable at $150 a pop. :-+
-
Would the Siglent SP3050A probes be ok aswell?
-
Would the Siglent SP3050A probes be ok aswell?
No first hand experience with them, but the other Siglent stuff I have is crazy good for the money.
-
Would the Siglent SP3050A probes be ok as well?
They are specified for the SDS5000X series but of course will work on a SDS2304X Plus however their compensation range is not quite as wide, 8-20pF vs 9-25pF for SP2035A.
Here are the production recommendations for probes:
https://siglentna.com/wp-content/uploads/dlm_uploads/2022/08/Probe_List_008102022.pdf
Quick overview of all the Siglent probes here:
https://siglentna.com/wp-content/uploads/dlm_uploads/2022/08/Probe_DataSheet-E01B.pdf
Remember for these models 500 MHz capability is only available on 2 channels and each must be on an ADC by itself or a 350 MHz BW filter will automatically engage so a couple of 500 and SP2035A 350 MHz probes will be the most cost effective solution.
https://siglentna.com/product/sp2035a-auto-sense-350-mhz-oscilloscope-probes/
https://siglentna.com/product/sp3050a-500-mhz-oscilloscope-probe/
-
Remember for these models 500 MHz capability is only available on 2 channels and each must be on an ADC by itself or a 350 MHz BW filter will automatically engage so a couple of 500 and SP2035A 350 MHz probes will be the most cost effective solution.
https://siglentna.com/product/sp2035a-auto-sense-350-mhz-oscilloscope-probes/
https://siglentna.com/product/sp3050a-500-mhz-oscilloscope-probe/
Nice smart note, 4 500MHz probes need another DSO with dedicated ADCs per channel, or much faster ADCs that are shared :-+
Best,
-
Remember for these models 500 MHz capability is only available on 2 channels and each must be on an ADC by itself or a 350 MHz BW filter will automatically engage so a couple of 500 and SP2035A 350 MHz probes will be the most cost effective solution.
https://siglentna.com/product/sp2035a-auto-sense-350-mhz-oscilloscope-probes/
https://siglentna.com/product/sp3050a-500-mhz-oscilloscope-probe/
Nice smart note, 4 500MHz probes need another DSO with dedicated ADCs per channel, or much faster ADCs that are shared :-+
Best,
Exactly. That's why I only procured 2 "real" 500 MHz probes. Only makes sense.
Another thing of note is that probes above 350 MHz are usually just 10X probes. This allows them to be compact and up to the task. You still need to keep around some probes that will do 1X for the rare applications you need those. So just don't go sell all your stock probes at a flea market. ;)
-
Remember for these models 500 MHz capability is only available on 2 channels and each must be on an ADC by itself or a 350 MHz BW filter will automatically engage so a couple of 500 and SP2035A 350 MHz probes will be the most cost effective solution.
I love the accessory kit that comes with the Siglent probes. It may have cost me less initially the way I went, but by the time I equipped myself with equivalent capabilities and taking into account the effort, I think it was a wash at best. If I was not retired with time on my hands it would be a no brainer to go with the Siglent probes.
-
I see from the opening post that the "keygen (https://repl.it/repls/DirectProbableTwintext)" consists of a file named "main.py" which includes this code...
import hashlib
SCOPEID = '0000000000000000'
Model = 'SDS2000X+'
bwopt = ('25M', '40M', '50M', '60M', '70M', '100M', '150M', '200M', '250M', '300M', '350M', '500M', '750M', '1000M', 'MAX', 'AWG', 'WIFI', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA')
hashkey = '5zao9lyua01pp7hjzm3orcq90mds63z6zi5kv7vmv3ih981vlwn06txnjdtas3u2wa8msx61i12ueh14t7kqwsfskg032nhyuy1d9vv2wm925rd18kih9xhkyilobbgy'
def gen(x):
h = hashlib.md5((
hashkey +
(Model+'\n').ljust(32, '\x00') +
opt.ljust(5, '\x00') +
2*((SCOPEID + '\n').ljust(32, '\x00')) +
'\x00'*16).encode('ascii')
).digest()
key = ''
for b in h:
if (b <= 0x2F or b > 0x39) and (b <= 0x60 or b > 0x7A):
m = b % 0x24
b = m + (0x57 if m > 9 else 0x30)
if b == 0x30: b = 0x32
if b == 0x31: b = 0x33
if b == 0x6c: b = 0x6d
if b == 0x6f: b = 0x70
key += chr(b)
return key.upper()
for opt in bwopt:
print('{:5} {}'.format(opt, gen(SCOPEID)))
QUESTIONS:
1. What is the step-by-step procedure for using "main.py" to generate and then use the keys?
2. Will generated keys work on the 2-channel SDS2102X Plus, even with latest firmware?
3. From reading some posts in this thread, it seems that 500MHz operation will be unlocked with a keygen-created key, but what other Software Options are unlocked? For example, is there a key to unlock the logic analyzer? (Bad idea to buy the expensive SPL2016 if the scope can't be unlocked to use it.) Arbitrary Waveform Generator? CAN FD Decoder? Etc.?
Thank you!
-
Hi,
1) It´s here (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-hack/msg3822731/#msg3822731).
2) Should work, I haven´t "heard" about any problems - Just try it..
3) See 1, it generates all the option keys - But it also generate keys you don´t need.
-
Hi,
1) It´s here (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-hack/msg3822731/#msg3822731).
2) Should work, I haven´t "heard" about any problems - Just try it..
3) See 1, it generates all the option keys - But it also generate keys you don´t need.
More correctly...can't use as they either don't apply to this instrument or are beyond its capabilities.
The risk of damage/bricking is ever present if care is not taken.
YMMV
-
Rob are right, so edit this line:
bwopt = ('25M', '40M', '50M', '60M', '70M', '100M', '150M', '200M', '250M', '300M', '350M', '500M', '750M', '1000M', 'MAX', 'AWG', 'WIFI', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA')
To:
bwopt = ('200M', '350M', 'AWG', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA')
And get only the keys you really need.
And don´t forget: ScopeID means not the serialnumber.
-
Rob are right, so edit this line:
bwopt = ('25M', '40M', '50M', '60M', '70M', '100M', '150M', '200M', '250M', '300M', '350M', '500M', '750M', '1000M', 'MAX', 'AWG', 'WIFI', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA')
To:
bwopt = ('200M', '350M', 'AWG', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA')
And get only the keys you really need.
And don´t forget: ScopeID means not the serialnumber.
So if one does not edit the code exactly as above, the scope will be bricked?
Also, why is there 200M and 300M in the above? Isn't the scope we are talking about either 100MHz or 200MHz or 350MHz or 500MHz as per the following product page?
https://siglentna.com/digital-oscilloscopes/sds2000xp/
If so, wouldn't it be best to mention those 4 values in the code/hack? Or if one only wants 200MHz, then one would need only use the following?
bwopt = ('200M', 'AWG', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA')
-
So if one does not edit the code exactly as above, the scope will be bricked?
No... ;)
It´s only a script, it needs the scoope id as input, from this it generates keys.
The outputs are the variables named "PWA", "AWG" and so on.
There are more variables than you´ll need, therefore I´ve suggested the edit.
It´s only for clarification, you can leave it as it is and pick only the keys you really need.
-
It´s only a script, it needs the scoope id as input, from this it generates keys.
I'm a little confused on which Scope ID is correct. If we go back to page 1 of this thread, we see Dave posting a text dump...
Scope ID: 00 00 00 00 00 00 00 00 00 00 00 00
8dd6-bb73-29a7
ScopeID(64): 4914a72973bbd68d
Then at 34:50 in Dave's video (https://youtu.be/HxzQS-Bn2R0?t=2090), we see the following info in System Status...
Scope ID: 0800-001b-3d4a-4d01
Now it's obvious that all of us are not to use his Scope ID, but I am asking WHICH Scope ID is correct, since his data dump shows multiple Scope IDs, and then the System Status shows yet another. Are we to use the Scope ID shown on the scope itself within System Status?
-
8dd6-bb73-29a7
-
8dd6-bb73-29a7
If correct, that means in order to do the HACK, we need to perform these steps...
1. Open the scope, as Dave does in his video at 23:40 (https://youtu.be/HxzQS-Bn2R0?t=1420).
2. Connect wires (how many though, I cannot see in Dave's video) to the rightmost to the right of the round battery on the scope's main board, then connect those wires to a USB-to-Serial interface, which in turn is connected to a computer with Terminal software set to COM9.
3. Soft power on the scope to see the data dump in the Terminal software.
4. Look for "Scope ID" with all those zeros, but then actually use the number on the line beneath, which in Dave's case was 8dd6-bb73-29a7.
Are my steps above correct? Or am I missing something? Also, how many wires is Dave connecting to the main board?
Still very confused as to why there are multiple Scope IDs, both in the data dump and then on the scope's UI within "System Status"!
-
NO!
The scope ID can be found on the System Status screen.
-
NO!
The scope ID can be found on the System Status screen.
Thank you for proving CORRECT information. I appreciate facts. Not sure why other people are posting only speculation.
By the way, why are there multiple Scope ID's as I mention in my previous post?
-
By the way, why are there multiple Scope ID's as I mention in my previous post?
I think only Siglent can answer that one ;D
Don’t panic too much over the scope ID and license keys generated by the script.
If you get anything wrong during the process, the keys simply won’t activate the wanted option.
-
Or pm the ID and get the keys.. ;)
-
I've actually not bought the scope yet. I've been mulling a purchase of the 2-channel version from TEquipment (a model which seems to have been discontinued, but still is in stock for a very reasonable price with EEVBlog discount). However, the cheapest price I've found is actually on Amazon Japan. Even so, it ships from Amazon but the seller is Aidetek, and on their Amazon Japan product page for the scope, they have a photo of a Siglent authorized distributor certificate which shows an address in California that leads to a private home for sale. I wrote Aidetek an email about that oddity and they replied back twice in broken English in a way that is not too reassuring, so I'm not sure if I would trust them, although their price is $100 less than TEquipment, and even cheaper when you consider shipping from Amazon Japan is free but shipping from TEquipment would be about $140 extra. Hmmm....
-
Not sure why other people are posting only speculation.
The only person posting speculation seems you... :-//
The process has been fully documented in this thread and others and you only raised questions that are unwarranted. I suggest you take advantage of Martin's proposal and pm him to get your licenses.
-
I've actually not bought the scope yet. I've been mulling a purchase of the 2-channel version from TEquipment (a model which seems to have been discontinued, but still is in stock for a very reasonable price with EEVBlog discount). However, the cheapest price I've found is actually on Amazon Japan. Even so, it ships from Amazon but the seller is Aidetek, and on their Amazon Japan product page for the scope, they have a photo of a Siglent authorized distributor certificate which shows an address in California that leads to a private home for sale. I wrote Aidetek an email about that oddity and they replied back twice in broken English in a way that is not too reassuring, so I'm not sure if I would trust them, although their price is $100 less than TEquipment, and even cheaper when you consider shipping from Amazon Japan is free but shipping from TEquipment would be about $140 extra. Hmmm....
No guessing required.
The official Siglent agents are listed here and I see 2 for Japan:
https://int.siglent.com/map/
-
I've actually not bought the scope yet. I've been mulling a purchase of the 2-channel version from TEquipment (a model which seems to have been discontinued, but still is in stock for a very reasonable price with EEVBlog discount). However, the cheapest price I've found is actually on Amazon Japan. Even so, it ships from Amazon but the seller is Aidetek, and on their Amazon Japan product page for the scope, they have a photo of a Siglent authorized distributor certificate which shows an address in California that leads to a private home for sale. I wrote Aidetek an email about that oddity and they replied back twice in broken English in a way that is not too reassuring, so I'm not sure if I would trust them, although their price is $100 less than TEquipment, and even cheaper when you consider shipping from Amazon Japan is free but shipping from TEquipment would be about $140 extra. Hmmm....
No guessing required.
The official Siglent agents are listed here and I see 2 for Japan:
https://int.siglent.com/map/ (https://int.siglent.com/map/)
I am not guessing. I am well aware of the "official" agents for Japan, all of whom have pricing well beyond the highly reputable TEquipment, as is typically for most product distributors in Japan. While the official agents in Japan can argue they provide all documentation in Japanese and full support in the Japanese language, that is, of course, not required at all for myself. I tend to focus on price for brand new items that are in pristine, unopened condition.
If an item is shipped by Amazon Japan (within Japan) but sold by a US vendor, I don't see that as a problem, necessarily. A lot of items on Amazon Japan are sold and shipped that way. But the US vendor in question ("Aidetek") showcases an authorized distributor certificate (see attachment below) from Siglent on Amazon Japan which has a California address that leads to a private home that is currently for sale. And that, to me, tends to be a bad sign. The price is listed as ¥119,000 which includes Japan's 10% sales tax and shipping is free. That is just about US$900 at today's exchange rate -- one of the lowest prices I've seen for the 2 channel SDS2102X. That's the main reason I emailed "Aidetek" to see how they responded. They wrote me two replies, the second of which provided a dead link to a website in California that confirms businesses in the state, which too is quite odd and unsettling...
FIRST REPLY (I had emailed them to ask if the item was new and unopened.)
Thank you very much for your inquiry, yes, we are authorized distributor in Japan from Siglent, this SDS2102X is a brand new and unopened unit with all standard accessories from Siglent, you can register your machine on Siglent website, it comes with 3 years warranty .
Please feel free to let us know if you have any further questions, thank you
Thanks and best regards,
Cherry Tan
www.aidetek.com (http://www.aidetek.com)
Tel: 408-329-7985
Fax: +866-571-5680
Email: cherry@aidetek.com
We sells surface mount SMD/SMT resistor kit, capacitor kit and inductor kit with our patented BOX-ALL enclosure. Also we a big supplier of low-cost handheld test equipment. We offer all kinds of Portable Digital Oscilloscope, FLUKE Multimeter, LCR meter, Clamp meter, network cable tester, test leads, process meter, free shipping worldwide with warranty, lowest price.
SECOND REPLY (I had mentioned their bad address on the certificate.)
Pease check status here:
https://businesssearch.sos.ca.gov (https://businesssearch.sos.ca.gov)
thank you
I can only guess the Siglent scope on Amazon Japan is a "gray market" item sold by a Chinese vendor possibly based in the USA. I've purchased gray market items before without issue, but never a scope. TEquipment may be the best option in the end overall, even if the total cost is higher (but still not as high as Japan Agent pricing).
-
I can only guess the Siglent scope on Amazon Japan is a "gray market" item sold by a Chinese vendor possibly based in the USA. I've purchased gray market items before without issue, but never a scope. TEquipment may be the best option in the end overall, even if the total cost is higher (but still not as high as Japan Agent pricing).
Then should be no problem as we can still source the 2ch X Plus therefore it's still a current western market product....not China only for which you will have zero western support.
-
Ok thanks to the discussion here I have now upgraded my 2104x plus to a 2504x plus,
Unfortunately while all the detail is in this thread, the thread is now 17 pages and it it took quite a bit of searching to find the one clue as to why initially entering the option codes kept failing.
Martin's step by step instruction did confirm that I was following the right process, however it missed one minor but critical point.
- You can find this post (which includes pictures) on page 10 - but if I may add a few additional comments here:
Taken some screenshots listed below, according to the "guide" step by step.
First you have to open the link mentioned in the very first post here.
Second you got the message like in pic 2, you have to login to continue.
Third I use my google-account for loggin in.
Fourth and fifth, you are now into the program, where you have to erase the "zeros" in SCOPE ID and fill in the ID of your scope.
Then press "Run"...
- I used Miyagi's link from page 1:
https://repl.it/repls/DirectProbableTwintext
Enter the scope ID as shown on the oscilloscope on the Utility/menu/System setting/system status/ screen except without the dashes,
so for example:
Scope ID: 0123-4abc-def1-2345
would be entered as
01234abcdef12345
- noting this is all in lower case letters
- also do not change the "model number" in the script, so leave the line :
Model = 'SDS2000x+'
- having said that, I do not know if this script is also used for upgrading other Siglent product lines, in which case it may be that this is for entering other base model numbers.
Sixth now you got a couple of license keys which you have to enter in the options menu.
The several bandwith license key are making no sense except the ones for 200,350 and 500Mhz.
This was it.
Or don´t you agree, gentlemen here ? ;)
I do agree, however the "Gotcha" here is that the script generates license in upper case, while the oscilloscope wants the keys in lower case.
So where the script generates for example:
200M ABCDEFGHJ1KLMN67
This needs to be entered as:
abcd efgh j1kl mn67
- Noting the bandwidth upgrades need to be entered in sequence, so to upgrade from 100Mhz to 500Mhz first you upgrade to 200Mhz, then 350Mhz, and finally 500Mhz.
- Also noting that while the oscilloscope prompts you to reboot after enter each key, this is not needed until you have entered the last key
-
...the "Gotcha" here is that the script generates license in upper case, but the oscilloscope wants the keys in lower case, so where the script generates for example:
200M ABCDEFGHJ1KLMN67
This needs to be entered as:
abcd efgh j1kl mn67
WITH SPACES like that?
-
...the "Gotcha" here is that the script generates license in upper case, but the oscilloscope wants the keys in lower case, so where the script generates for example:
200M ABCDEFGHJ1KLMN67
This needs to be entered as:
abcd efgh j1kl mn67
WITH SPACES like that?
The window to enter the code breaks it up into 4 x 4 digit boxes, so it forces you to add spaces.
- As you will see if you look at Martin72's post on page 10 of this thread
-
I received a SDS2104 yesterday. The bandwidth upgrade works but the options upgrades give me an invalid data message and the key is not applied. It looks like keygen.py uses scopeid for the bandwidth keys and uses SN for the other options. I checked the SN on the box, that back of the scope and the Web GUI and they all agree. Also, the Bode plot csv save file includes the SN and it matched the other three sources. The firmware is 1.5.2R2, I downgraded to 1.3.9R12 and tried again but still the option keys did not work. I am stuck. Does anyone have any suggestions?
Thanks,
Tom
-
By what means did you run the script?
This is the script I used. And I ran it on my own install of Python 3.6.1. It only needs the scope ID and the Model. Enter the SCOPEID without spaces.
import hashlib
SCOPEID = '0123456789abcdef'
Model = 'SDS2000X+'
bwopt = ('100M', '200M', '350M', '500M', 'AWG', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA', 'MANC', 'SENT')
hashkey = '5zao9lyua01pp7hjzm3orcq90mds63z6zi5kv7vmv3ih981vlwn06txnjdtas3u2wa8msx61i12ueh14t7kqwsfskg032nhyuy1d9vv2wm925rd18kih9xhkyilobbgy'
def gen(x):
h = hashlib.md5((
hashkey +
(Model+'\n').ljust(32, '\x00') +
opt.ljust(5, '\x00') +
2*((SCOPEID + '\n').ljust(32, '\x00')) +
'\x00'*16).encode('ascii')
).digest()
key = ''
for b in h:
if (b <= 0x2F or b > 0x39) and (b <= 0x60 or b > 0x7A):
m = b % 0x24
b = m + (0x57 if m > 9 else 0x30)
if b == 0x30: b = 0x32
if b == 0x31: b = 0x33
if b == 0x6c: b = 0x6d
if b == 0x6f: b = 0x70
key += chr(b)
return key.upper()
for opt in bwopt:
print('{:5} {}'.format(opt, gen(SCOPEID)))
Update:
I just ran it again by pasting it in here : https://www.programiz.com/python-programming/online-compiler/ (https://www.programiz.com/python-programming/online-compiler/)
It ran correctly, so you don't need to install Python if you don't want to.
-
Thanks Bill.
Your version on keygen.py generated different option keys and they all worked.
I have tried two different keygen version I downloaded from this thread and they did not generated the correct option keys but yours did.
I am using python 3.11.2 on MacOS 13.3.1, and use Visual Studio Code 1.75.1.
Tom
-
Hi,
PM me your scope id, let´s check if I could generate the correct keys for your scope too...
-
Hello, I just bought a sds2102x plus.
Using the script I saw that the scope ID and the instrument model must be entered.
It is originally SDS2000X+, I have to change in SDS2102X+ or I leave it unchanged?
Thank you!!!!!
-
Leave it at SDS2000X+.
-
Ok, all the options works.
I have sds2102x plus, siglent sell only the 350mhz option,
For 350mhz bandwidth, i must use 200mhz before 350 or directly 350?
-
You have to do it step by step
100->200->350->500
-
Thank you!!!!!!
-
I didn't want to mess around with my 2104X, but then I realised the AWG is only installed temporarily.... :palm:
So I installed the Function Generator Option as described in this thread which worked fine. But now every time I'm running the Bode Plot the oscilloscope completely freezes! Anybody else experienced this? What can I do now, any suggestions?
-
Bode plot slows the system "massively" down when active, or is the scope freezing completely (no plot lines will be drawing) ?
-
The scope is freezing completely! No plot lines are drawn, time stops and there is no response to pushing buttons or the screen. So the only thing I can do is to restart the scope by holding the power button for a few seconds...
-
Never had the problem, which firmware ? Latest ?
-
1.3.9R10
Do you think updating the firmware could help?
-
1.3.9R10
Do you think updating the firmware could help?
Or just do a reset to the config in order to reset config structures for the gen. Maybe it is using garbage values...
-
Yepp, but additionally I would upgrade to the latest version..
Possibly the red framed is in a certain connection with his problem.
-
I installed the latest firmware (1.5.2R3) and indeed, the problem is gone! :-+
Thank you for the help!!
-
The usual group of super contributors helped me here a while back (thank you all) and I was able to "freshen" my SDS's capabilities. The python code that helped me do this was all over this topic. I have recently added to the Siglent stable with a new SSA3021X+ and was over at that thread but the locations for the SSA kgen for that guy are no where to be found. Discussions of the same over in SSA land are very subdued or mixed with non-plus procedure. Not so here. Sorry for the post here rather than over at SSA. It is like the SSA police are watching over there. I'm scared. :scared:
I would assume that the SDS kgen will not work with SSA equipment. Just need some help to get to the SSA python code.
-
Works everytime! Post it and ye shall find. No less that 1 minute after posting I found my missing py. Ok now you can yell at me for asking a frequency question in the time domain.
Seriously, Siglent should pay all of you. You rock.
-
I would greatly appreciate it if someone could provide insight. I've upgraded the Siglent SDS2204X Plus to 500MHz using a Python script, yet it still runs on the old firmware. Does anyone know whether the upgrade would be disrupted if I update the firmware to the latest version?
-
Does anyone know if there is a wifi adapter that i can use it with Siglent SDS2204X Plus?
-
I would greatly appreciate it if someone could provide insight. I've upgraded the Siglent SDS2204X Plus to 500MHz using a Python script, yet it still runs on the old firmware. Does anyone know whether the upgrade would be disrupted if I update the firmware to the latest version?
The firmware updates will be fine. The python script produces valid and 100% authentic licenses.
-
Does anyone know if there is a wifi adapter that i can use it with Siglent SDS2204X Plus?
Not that I'm aware of.
-
Does anyone know if there is a wifi adapter that i can use it with Siglent SDS2204X Plus?
For WiFi to work it first must have a I/O menu to enter the access point settings, only 4ch X-E and 2000X-E have that.
-
Does anyone know if there is a wifi adapter that i can use it with Siglent SDS2204X Plus?
I'm using a TP-Link router in client mode, works fine.
https://www.tp-link.com/us/home-networking/wifi-router/tl-wr902ac/ (https://www.tp-link.com/us/home-networking/wifi-router/tl-wr902ac/)
-
could you share more information please. Are you still using a network cable to connect to this router with scope? Or are you confirming that a wifi adapter could be plugged into the USB port and it can connect to a wifi..
-
could you share more information please. Are you still using a network cable to connect to this router with scope? Or are you confirming that a wifi adapter could be plugged into the USB port and it can connect to a wifi..
SDS2000X Plus does not support USB WiFi dongles at the time. Any of them. There is no support for them. Tautech explained it.
People shared few names of very small routers that have Ethernet ports where scope can be connected..
-
Regarding the problem of SDS2000X Plus connecting to WIFI, I have a cheap and simple solution: buy a TL-WR802N mini router, the price is 12 US dollars, use the client mode, and connect the oscilloscope with a network cable. At this time, the router is equivalent to a wireless network card.
-
So these do go to 500MHz BW, and all have the same hardware. I can get 1 in a month, or wait and see what the sds1000X HD will be like. But that's more of a side grade, for 12bit resolution. I can do that later, and sell my 1204X-E.
I should get the 2104Xplus in a month or 2.
-
I'm getting a 2104xplus in 3 weeks, it should be already licensed for 200MHz. Or is that something I have to do on my own, 1st. And should I update firmware 1st or after ? (Will it still be labeled 2104 on the physical logo/label ?) Just skimming through this thread, there's a lot of little details I might be missing.
So when I get the scope and make sure the basic's are working, do I hook it up to PC, goto the web-based SPCI page, like with my 1204x-e ? Then find the scope ID and the Model, so would that be something like 2204 if it's lic'ed for 200MHz ?
And then take those, and enter them lower-case, into the below python script, for SCOPEID, Model.
Am I supposed to remove some of the stuff in the script that's not for the 2104x+ ?
And do I have run this multiple times to get a key, for each BW step up, and for each SW package I want to unlock ??
Is there any modern video on this ? I know very little about Python, I tried super basic stuff years ago.
The link on page 1 takes me no where, or am I supposed to sign up? Was that the same as the script ?
What else am I missing ?
Here's what I assume is the thing to use
By what means did you run the script?
This is the script I used. And I ran it on my own install of Python 3.6.1. It only needs the scope ID and the Model. Enter the SCOPEID without spaces.
import hashlib
SCOPEID = '0123456789abcdef'
Model = 'SDS2000X+'
bwopt = ('100M', '200M', '350M', '500M', 'AWG', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA', 'MANC', 'SENT')
hashkey = '5zao9lyua01pp7hjzm3orcq90mds63z6zi5kv7vmv3ih981vlwn06txnjdtas3u2wa8msx61i12ueh14t7kqwsfskg032nhyuy1d9vv2wm925rd18kih9xhkyilobbgy'
def gen(x):
h = hashlib.md5((
hashkey +
(Model+'\n').ljust(32, '\x00') +
opt.ljust(5, '\x00') +
2*((SCOPEID + '\n').ljust(32, '\x00')) +
'\x00'*16).encode('ascii')
).digest()
key = ''
for b in h:
if (b <= 0x2F or b > 0x39) and (b <= 0x60 or b > 0x7A):
m = b % 0x24
b = m + (0x57 if m > 9 else 0x30)
if b == 0x30: b = 0x32
if b == 0x31: b = 0x33
if b == 0x6c: b = 0x6d
if b == 0x6f: b = 0x70
key += chr(b)
return key.upper()
for opt in bwopt:
print('{:5} {}'.format(opt, gen(SCOPEID)))
Update:
I just ran it again by pasting it in here : https://www.programiz.com/python-programming/online-compiler/ (https://www.programiz.com/python-programming/online-compiler/)
It ran correctly, so you don't need to install Python if you don't want to.
-
I'm getting a 2104xplus in 3 weeks, it should be already licensed for 200MHz. Or is that something I have to do on my own, 1st. And should I update firmware 1st or after ? (Will it still be labeled 2104 on the physical logo/label ?)
You may get it without the free BW upgrade option installed.....depends on how your supplier flies.
We install so customers don't need to, takes just a minute of 2 when you've done lots. ;)
If not installed you should get a license authorization code to redeem for the actual real license code at the Siglent licensing website and instructions on how to do that.
Sys Info is the only place that will display the model has changed from labeled.
Firmware updates have zero impact on any option licensing.
-
and i def want the 120
Sure you´re in the right thread ?
-
thanks i accidentally posted on the wrong thread.
-
Here's what I assume is the thing to use
Blah, blah, ...
You would use this if you wanted to generate all available license keys.
I should mention that it is best to apply the BW keys in order (200 then 350 then 500). When I tried to go directly to 500 the license was accepted strange things happened. The model number changed to "SDS2504X Plus" but the response was very strange and distorted HF waveforms were the result. Luckily this was reversible and when I did them in order the results were spectacular.
-
Regarding the problem of SDS2000X Plus connecting to WIFI, I have a cheap and simple solution: buy a TL-WR802N mini router, the price is 12 US dollars, use the client mode, and connect the oscilloscope with a network cable. At this time, the router is equivalent to a wireless network card.
Fantastic little device. :clap:
Just got mine working and it's totally invisible to your devices when in Client mode.
However when looking locally for one they were nothing like 12USD and I succumbed to one from Aliexpress. ::)
Well I paid for that in that the configuration UI was in Chinese with no apparent way around it but with a lot of Copy/Paste into Google Translate I finally got the thing to work. :phew:
Advice to westerners, get a English UI model so to not be confronted with this:
(https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-hack/?action=dlattach;attach=1805273)
There is a good amount of configuration required and done in Access Point mode before change to Client mode and all of which would be so much easier if you can read Mandarin. :horse:
Nevertheless I got it to work in the end so carrying equipment that normally requires a wired LAN connection to your network for remote access is no longer required. 8)
Tests with SDS1104X-E (yes I do have the USB WiFi dongle too) with NTP time server and a SVA1000X analyzer/VNA, both connected to an iPad just fine and each of them communicated with our WiFi router DHCP for IP addresses fine also demonstrating TL-WR802N is invisible to devices that connect to you LAN via it.
-
Yee-haw, I just ordered the 2104Xplus and with the 200MHz upgrade included for free. This scope should last me, until it or me, fall apart. And being so small, I can use it and my 1204x-e at the same time on the bench, if I ever wanted to.
-
Regarding the problem of SDS2000X Plus connecting to WIFI, I have a cheap and simple solution: buy a TL-WR802N mini router, the price is 12 US dollars, use the client mode, and connect the oscilloscope with a network cable. At this time, the router is equivalent to a wireless network card.
Fantastic little device. :clap:
Just got mine working and it's totally invisible to your devices when in Client mode.
However when looking locally for one they were nothing like 12USD and I succumbed to one from Aliexpress. ::)
The price jumped to $30 here. For that, I'd pay the extra $10 and get the TL-WR902AC if I was going to go wireless.
-
so the 2104x plus showed up today got a great deal its brand new. i see some saying you have to go 100-200-350 etc but since this is already 100 do i still do 100 or do i start with 200 then go up from there?
and is there one script that is reliable and works every time i see a few different ones listed and i dont want to screw this thing up all the other siglent's were easy as can be but this is my most pricey one currently and i want to go to 500. BUT if i do 500 does that in turn make this oinly a 2 channel scope or can i still use it at 350 4 channel and then when i want to use 500 i can just use 2 channels of it vs 4?
thank you as always for all your help. i have read this whole thread now but these questions are still kind of sitting in my mind before i start
-
Hi,
You buy a SDS2104X+, that already has 100Mhz, so you don't need another key for this frequency.
You can upgrade to SDS2504X+, that means you have 500Mhz bandwidth on 2 channels(1+3, 2+4, 1+4, 2+3).
If you use more than 2 at the same time, the bandwidth automatically drops back to 350Mhz.
Also if you use 2 channels of a single ADC (1+2 or 3+4), the bandwidth drops back to 350Mhz.
Either way, with the upgrade to 2504 you will have at least 4 channels and 350Mhz.
You don't have to make single steps and upgrade step by step from 200Mhz to 500Mhz, you can use the key for the 500Mhz right away.
The key generator works, you only have to enter the keys once and then the scope is upgraded "forever".
-
Trying to understand this text...
Why do you do such things?? :-//
-
You´re right, sry.
-
ok great. i was reading some pages back where people were doing it in steps thats why i was confused.
-
I'm almost certain I remember it needing to be done in steps as well. Thats how I did it on mine. 100->200->350->500. It was already 100 when I started so the first license I installed was the 200.
-
so the 2104x plus showed up today got a great deal its brand new.
It should have arrived with the free 200 MHz BW upgrade !
If not already installed (check System Info) insist your supplier provides the free BW upgrade license !
-
I'm almost certain I remember it needing to be done in steps as well.
Hmmm...Was it so...too long ago for me.
-
hmmm so should i put them in one at a time just to be safe then? and can we do the commands over the web interface or do we have to use telnet like for the waveform generator?? i have the interface up and running now
-
so the 2104x plus showed up today got a great deal its brand new.
It should have arrived with the free 200 MHz BW upgrade !
If not already installed (check System Info) insist your supplier provides the free BW upgrade license !
i dont see anywhere it shows its been updated. still shows 2104x plus in the info screen
no it was def not updated to 200 this unit. but using the commands its now a 2504x plus. now to add all the extras in there. this one was actually REALLY easy to do. i ended up doing them one at a time just to be on the safe side i rebooted between each one. this also showed me if the upgrade stuck after a reboot. so far so good
okay need help one more time and i think i got them all where do i find the 2000xp_fg code and the 2000xl_16la code? i tried all of them none work for those two. was i supposed to put those in before doing the 500 upgrade? all the rest of them took fine. mine doesnt show mso or awg in the options menu to install either? help me out please and then im done with upgrades for a while. im lost with these two. thank you
-
so the 2104x plus showed up today got a great deal its brand new.
It should have arrived with the free 200 MHz BW upgrade !
If not already installed (check System Info) insist your supplier provides the free BW upgrade license !
i dont see anywhere it shows its been updated. still shows 2104x plus in the info screen
no it was def not updated to 200 this unit.
FYI:
https://siglentna.com/news-article/2000-series-oscilloscope-power-up-promotion/
Your reseller has slipped up and now owes you !
That was a $1200 upgrade for free !
-
i cant complain to much for what i paid but yeah ill contact them and see what they say.
and for some reason using the web interface for the fg and 16la worked fine no idea why it wouldnt take them from the front of the unit. but they are all unlocked now. the fg is the awg and tbe 16la is the mso (which is what i figured they were).
according to that page i just fill out the form and they send me the upgrade card (which i dont really need now lol) but i guess ill take it anyway. i may be ordering another one of these for my other office im torn between another one of these and another brand to have something different. we will see. i love that these can be upgraded so easily though. everything seems to be working now. i still cant figure out why it took the codes from the web interface but refused them all from the front of the unit. every code went through fine when i added them into the web interface but all of them said invalid from the front of the unit. and i triple checked every code they were all put in correctly and all in lower case. oh well they are in now but still doesnt make any sense.
i doubt ill get anywhere with them regarding anything with the 200 upgrade. i got 35% off the unit which was already on sale for around 1050. so im not worried about it at this point. i had a damaged shipment and they made good by giving me the code for that discount so i took the code and grabbed one of these since ive been eyeing them for a while. i could have spent more but this will im sure serve my purposes for now.
-
It should have arrived with the free 200 MHz BW upgrade !
If not already installed (check System Info) insist your supplier provides the free BW upgrade license !
Doesn't it seem like you can register your scope at the bottom of the promo page, and have Siglent e-mail the license card ?
(https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-hack/?action=dlattach;attach=1843225)
/Bingo
-
ok great. i was reading some pages back where people were doing it in steps thats why i was confused.
You do need to do it in steps. The different steps effect more than just the VGA. Other parts of the scope get changed. If you go directly to 500 without going first to 200 and then 350 you will get strange performance. Maybe you just need to do the 200 or the 350, but one of those enables something that if it is not enabled 500MHz does not operate correctly. You will not have 500MHz BW and higher frequency signals will be significantly distorted. It only takes a few seconds to do each BW license and re-boot so it's not much of an effort.
Not only has this been tested and verified, it is quite telling to note that Siglent do not sell a direct 100 - 500 license or 200 - 500 license. Only a 350 to 500 license.
-
thats what i thought so im very glad i did it that way. but being it started at 100 already did i need to do 100 first? then 200 etc? i started with 200, then 350, then 500.
and does anyone know why it didnt show the first two options as the correct name when putting the codes in for those 2? where the fg is awg and the 16la is the mso? will everything be okay now? it took them and they show they are activated permanently. but as i said for some reason it would only accept them from the web address and not the front of the unit so i found that odd ive done a bunch now and know for sure how to enter the codes all lower case and in the right boxes of 4 etc. i just want to be sure it will function properly now.
thank you so much for your time and help with this. i really appreciate it very much.
-
thats what i thought so im very glad i did it that way. but being it started at 100 already did i need to do 100 first? then 200 etc? i started with 200, then 350, then 500.
No, you did not need to do 100 first. Just 200, 350 then 500. However, there will be no harm in doing the 100 first. Just a few seconds lost.
and does anyone know why it didnt show the first two options as the correct name when putting the codes in for those 2? where the fg is awg and the 16la is the mso? will everything be okay now? it took them and they show they are activated permanently. but as i said for some reason it would only accept them from the web address and not the front of the unit so i found that odd ive done a bunch now and know for sure how to enter the codes all lower case and in the right boxes of 4 etc. i just want to be sure it will function properly now.
thank you so much for your time and help with this. i really appreciate it very much.
Can you post images of your information screens ("System Info" and "Software Options")?
-
thats what i thought so im very glad i did it that way. but being it started at 100 already did i need to do 100 first? then 200 etc? i started with 200, then 350, then 500.
and does anyone know why it didnt show the first two options as the correct name when putting the codes in for those 2? where the fg is awg and the 16la is the mso? will everything be okay now? it took them and they show they are activated permanently. but as i said for some reason it would only accept them from the web address and not the front of the unit so i found that odd ive done a bunch now and know for sure how to enter the codes all lower case and in the right boxes of 4 etc. i just want to be sure it will function properly now.
thank you so much for your time and help with this. i really appreciate it very much.
There is no upgrade code for 100, it starts that way. You did it fine.
The names are basically the same thing in different forms:
FG = Function Generator = AWG = Arbitrary Waveform Generator.
16LA = 16 Channel Logic Analyzer = MSO = Mixed Signal Oscilloscope.
In this case the MSO really means they added a logic analyzer probe connection to the front of the DSO. Which is also an SPO, just to add to the confusion. 😉
-
There is no code for 100, it starts that way.
Sure there is. One can always see the associated BW code by doing SCPI:
MCBD?
-
There is no code for 100, it starts that way.
Sure there is. One can always see the associated BW code by doing SCPI:
MCBD?
I meant no upgrade, since it starts that way. 😉
-
I meant no upgrade, since it starts that way. 😉
I believe that but even the "starts that way" means Siglent had to assign that BW through a code. AFAIR the absence of a code isn't BW=100MHz.
-
I believe that but even the "starts that way" means Siglent had to assign that BW through a code. AFAIR the absence of a code isn't BW=100MHz.
Maybe absence of a code = 2GHz 🤣🤣
-
Maybe absence of a code = 2GHz 🤣🤣
You're right. It wouldn't be the first time for Siglent with previous equipments!! ;D
-
]You do need to do it in steps. The different steps effect more than just the VGA. Other parts of the scope get changed. If you go directly to 500 without going first to 200 and then 350 you will get strange performance. Maybe you just need to do the 200 or the 350, but one of those enables something that if it is not enabled 500MHz does not operate correctly. You will not have 500MHz BW and higher frequency signals will be significantly distorted.
If this is the case, I would be interested to know why in a technical sense.
All bandwidth variants have the same board, do you have to "get used to" the board that it no longer reaches up to 100Mhz, but higher?
Would really interest me.
Yes, the bandwidths are indeed staggered, must have a reason.
With the 2000HD, on the other hand, there is a license that directly unlocks from 100 to 500Mhz.
-
If this is the case, I would be interested to know why in a technical sense.
So would I.
The only thing I can think of is that at least two different methods are used to achieve the results and that different licenses enable to eh different methods.
I'm not sure Siglent would be keen on letting use know.
Perhaps there is a clue in the specs from the data sheet. For 100MHz, 200MHz and 350MHz the ratio between quoted BW and risetime is 0.35, however for 500 MHz the ratio is 0.4.
My guess is you could go directly from 100 to 350, then successfully install the license for 500MHz.
Does anyone know what VGA is used in this scope?
Edit:
Seems it's a LMH6518. So no real help there as all BW options are simply programmable up to 900MHz. All the lower BW would be implemented with first order filters internally. The only clue is still in the .4 ratio from the Siglent data sheet. Maybe the 350 MHz is selected via the VGA and the 500MHz is some kluge on that rather than enabling the 650MHz filter in the 6518. Perhaps a high pass filter in the jfet front end to boost gain at higher frequencies? :-//
-
My guess is you could go directly from 100 to 350, then successfully install the license for 500MHz.
Whether that would work or not, I don't know. However, if you check their site, they only offer stepping BW upgrades, none of the options for the SDS2000XP skip BW levels.
-
Whether that would work or not, I don't know. However, if you check their site, they only offer stepping BW upgrades, none of the options for the SDS2000XP skip BW levels.
Yeah, I don't know what's up with that. If you look at the spec sheet for the VGA/PGA each BW option (20, 100, 200, 350, 650, 700, 900) are all just selectable with a single code sent to it through it's serial (I2C) interface. Maybe there is something in firmware to discourage someone buying the 500MHz license and installing it on a 100MHz licensed unit. :-//
Edit:
It seems there may be another clue in the fall-back to 350MHz if more than 2 channels are enabled. Perhaps the 500MHz is acheived through enhanced sampling?
-
It seems there may be another clue in the fall-back to 350MHz if more than 2 channels are enabled. Perhaps the 500MHz is acheived through enhanced sampling?
On the same ADC.
These scopes have 2 ADC's and the BW limit is automatically engaged when you activate a 2nd channel.
1 ch on each ADC meets Nyquist and SW allows for 500 MHz capability.
-
On the same ADC.
These scopes have 2 ADC's and the BW limit is automatically engaged when you activate a 2nd channel.
1 ch on each ADC meets Nyquist and SW allows for 500 MHz capability.
That's probably how it's done.
-
On the same ADC.
These scopes have 2 ADC's and the BW limit is automatically engaged when you activate a 2nd channel.
1 ch on each ADC meets Nyquist and SW allows for 500 MHz capability.
That's probably how it's done.
::)
Sit down with yours, nothing connected and engage/disengage channels and you will see.
Sampling rate and mem depth change with active channels.
4ch X-E are similar dividing sampling and mem depth relative to channels engaged.
-
Sit down with yours, nothing connected and engage/disengage channels and you will see.
Sampling rate and mem depth change with active channels.
4ch X-E are similar dividing sampling and mem depth relative to channels engaged.
Yep, I'm aware of that.
-
Hi,
I'm playing around with the scope for a few days, and not everything works as before. Here is a quick summary:
Scope: SDS2104X plus, firmware: 1.5.2R3, hardware: 05-05.uboot: 5.4
- All license keys generated by python script are valid.
- It is not possible to get "telnetd" running with scpi "SHELLCMD" nor with "siglent_device_startup.sh" file on USB stick.
To run telnet I had to get serial console (soldering on mother-borad involved) and work from there. Having full access I've first tried to change root password with passwd and it worked (had to remount /usr/bin/siglent partition as rw before), however telnet login seems strange. I could login via network as "root" and my new password was accepted, but I did not get full root privileges. Skipping password checking with "telnetd -l /bin/sh" however did the trick.
I also tried some ways (found on other threads) to run telnetd permanently, but nothing worked. Finally I modified "/usr/bin/siglent/product_rcs_begin.sh" by adding "/usr/sbin/telnetd -l /bin/sh" line (of course also remount,rw /usr/bin/siglent is needed).
One more funny thing: there are some "options_***_times.txt" files in "/usr/bin/siglent/usr/usr", the seem to contain number or left uses of all options. If someone does not want to add permanent licenses it is very likely that modifying these files will do the trick.
And finally a question: there is a "Developer options" submenu in "Utility -> Maintenance", that asks for a password. What is is menu? Is password known? I've tried my own root password set by passwd before, but no luck.
Best Regards,
Michael W.
-
And finally a question: there is a "Developer options" submenu in "Utility -> Maintenance", that asks for a password. What is is menu? Is password known? I've tried my own root password set by passwd before, but no luck.
Try "siglentcd" and report back.
-
Success, Thank You!!
It gives access to temperature monitoring, boot times counter, some calibration data manipulation and FSP debug (don't know what it does). Anyway it is nice to have full access to the scope.
-
And what is more important - the possibility to save factory CAL data.
tnx2tv84
Markus
-
Does anyone know of a file I can modify to add a boot-time invocation of telnetd, that will survive a firmware update on an SDS2000X from V1.3.9R6 to V1.5.2R3?
I'd like to move to the new firmware, but rely on the telnet interface for various mods. Like monitoring device temps to calibrate a PWM fan replacement, maintain the clock on localtime with ntpd, etc.
I'd prefer not to solder on a UART header...
Thanks,
Craig
-
Does anyone know of a file I can modify to add a boot-time invocation of telnetd, that will survive a firmware update on an SDS2000X from V1.3.9R6 to V1.5.2R3?
I'd like to move to the new firmware, but rely on the telnet interface for various mods. Like monitoring device temps to calibrate a PWM fan replacement, maintain the clock on localtime with ntpd, etc.
V1.5.2R3 is mainly housekeeping of minor production changes whereas V1.5.2R1 has fixes and enhancements for numerous issues:
Measurement enhancement - Added setup/hold time: tsu@R, tsu@F, th@R, th@F
Optimized UI
Added SCPI commands for Measure Cursors and clearing measure items in Simple mode
Supported LXI (only with the Uboot-OS Version 5.4)
Supported time zone setting
Fixed several bugs
Webserver doesn’t show instrument UI if the scope reboot with a wireless mouse connected
Incorrect “Recall”icon in the File Manager
Scope freezes with AWG enabled and measure cursor on rise time
IP setting of AWG in Bode Plot not remembered after reboot
Network storage only works for SMB1.0
MEAS:SIMPle:ITEM\sOVSN,ON does not work as expected
Roll time incorrect at 1ks/div and 20kpts
Raw data not consistent in x and sinx/x interpolation modes
Math: Dx parameter of Derivation cannot be increased by universal control
Incorrect FFT sample rate
https://int.siglent.com/upload_file/zip/firmware/Oscilloscope/SDS2000X%20Plus_V1.5.2R1_EN-2.zip
However its always best to install the latest version.
-
Yes, I'd read the release notes, and it looked like a worthwhile update. I also noted from other posts, that I would loose the "siglent_device_startup.sh" trick via USB stick, and I would really like to maintain shell access to the scope. Thus, wondering if there is a means to make a persistent file-system change prior to updating.
Craig
-
I must say I'm loving this scope so far. I got the legit 200MHz upgrade when I bought the sds2104x+ a few months ago. So of all the things I would like to unlock, can I unlock the full 500MHz BW ? I've never used a scope over 200MHz, so I'd love to try it out.
I've read through some of these 2000x+threads before, and I've unlocked my PSU, AWG, and sds1104x-e=>1204. How hard is it to unlock these? What page are the key instructions on ?
-
Same process, same script. :popcorn:
-
What page are the key instructions on ?
Simply use the search function in this topic.
-
Hmm my probes are only rated for 100 and 200MHz, and I seem to remember 500MHz probes and actives probes costing a fortune. I forgot about that part.
-
Hmm my probes are only rated for 100 and 200MHz, and I seem to remember 500MHz probes and actives probes costing a fortune. I forgot about that part.
Do you really have a needs to use probes with HF > 200Mhz? Most people use appropriate terminated coax cable.
I bought the SDS2104X+ in Dec 2022, it was one of my best purchases in last 20 years. Unlocking all futures using the Python script was done in ~20 minutes.
-
Hmm my probes are only rated for 100 and 200MHz, and I seem to remember 500MHz probes and actives probes costing a fortune. I forgot about that part.
Not as bad as you think. And there's a project with a 2GHz active probe being developed by a user here for under $200.
Also, this was done with a coax cable:
(https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-hack/?action=dlattach;attach=1940727;image)
-
Yeah I don't have any coax besides scrap cable TV coax, which I can't connect to anyways, and yeah it's probably 70ohm or something.
I have to get all that stuff and and NanoVNA this winter, but after some computer upgrades. There's a refurbished SVA3021X on sale now, I'd love to get that, but I better learn on a NanoVNA, and I want those PC upgrades 1st.
Yeah I've seen that probe project, I would get 1. I was going to try making some real cheap/simple HF probe, I have to find Dave EEV video.
I have a few semi-broken 100-200MHz probes. I wonder what I can do with them.
-
The source in my screenshot is a TinySA Ultra. It's pretty cute, but I got it because of TEAS, not because I have a use for it beyond that png. 🤣
-
There's a refurbished SVA3021X on sale now, ...........
No such model. ;)
I have a few semi-broken 100-200MHz probes. I wonder what I can do with them.
Scope probes use a lossy coax which wouldn't be much use for the very low signal levels an analyzer can resolve.
-
Hello, I have a SDS2104x+ (100MHz) upgraded to SDS2504X+ (500MHz) with the hack, however, I am unable to upgrade my software options. I have used the generated codes for my unique ScopeID, SerialNumber and Model, but the scope returns "The data is invalid!". Any suggestions? Thanks.
Edit: Additionally, I have tried using the SCPI command: LCISL optioncode hexkey, to no avail. Restarting the scope before entering a new code and downgrading to the original 100MHz to enter the keys.
Finally figured it out after trying things for ages until finally some software option keys worked.
Previously, I was using a script that required the option keys to be generated using serial number. I changed script to the one provided by @Elasia, and boom it worked.
Leaving this here for anyone else that comes across a similar situation. Note all software keys are lowercase input through UI. I put the keys in while on my original scopes bandwidth (not sure if that changed anything at all). :-//
import hashlib
SCOPEID = '0000000000000000'
Model = 'SDS2000X+'
bwopt = ('25M', '40M', '50M', '60M', '70M', '100M', '150M', '200M', '250M', '300M', '350M', '500M', '750M', '1000M', 'MAX', 'AWG', 'WIFI', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA', 'MANC', 'SENT')
hashkey = '5zao9lyua01pp7hjzm3orcq90mds63z6zi5kv7vmv3ih981vlwn06txnjdtas3u2wa8msx61i12ueh14t7kqwsfskg032nhyuy1d9vv2wm925rd18kih9xhkyilobbgy'
def gen(x):
h = hashlib.md5((
hashkey +
(Model+'\n').ljust(32, '\x00') +
opt.ljust(5, '\x00') +
2*((SCOPEID + '\n').ljust(32, '\x00')) +
'\x00'*16).encode('ascii')
).digest()
key = ''
for b in h:
if (b <= 0x2F or b > 0x39) and (b <= 0x60 or b > 0x7A):
m = b % 0x24
b = m + (0x57 if m > 9 else 0x30)
if b == 0x30: b = 0x32
if b == 0x31: b = 0x33
if b == 0x6c: b = 0x6d
if b == 0x6f: b = 0x70
key += chr(b)
return key.upper()
for opt in bwopt:
print('{:5} {}'.format(opt, gen(SCOPEID)))
-
Hello, I have a SDS2104x+ (100MHz) upgraded to SDS2504X+ (500MHz) with the hack, however, I am unable to upgrade my software options. I have used the generated codes for my unique ScopeID, SerialNumber and Model, but the scope returns "The data is invalid!". Any suggestions? Thanks.
Edit: Additionally, I have tried using the SCPI command: LCISL optioncode hexkey, to no avail. Restarting the scope before entering a new code and downgrading to the original 100MHz to enter the keys.
Hello, i have the same thing as hardware here.
Strange is: I have hacked it to a SDS2204X + via Touchpanel - but can't get back. So i tried it via the Webfrontend with SCPI,
there it worked. Also up to 500MHz SDS2504X + in SystemInfo.
A day later i tried to toggle again, with the stored keys that i got by the script, and again is it not working.
Maybe there is a counter or something else that prevents from switching down and up?
BTW: I have to thank many users here for all the informations that i've found here!
-
I might be wrong, but AFAIK "downgrading" (removing software options) via SCPI is not supported.
-
I might be wrong, but AFAIK "downgrading" (removing software options) via SCPI is not supported.
But it should be possible to downgrade BW via MCBD command.
-
I might be wrong, but AFAIK "downgrading" (removing software options) via SCPI is not supported.
But it should be possible to downgrade BW via MCBD command.
Up- and downgrade Bandwidth via MCBD command IS possible. I did it both ways.
>> it has to be done step by step 100/200/350/500. 100>350 might work directly - 100>500 does not work in one step.
-
I might be wrong, but AFAIK "downgrading" (removing software options) via SCPI is not supported.
But it should be possible to downgrade BW via MCBD command.
100% for my personal explorations…….
This is my first test after generating licenses to be sure you can.
Normally not required other than a double check the script generates the correct ones.
-
>> it has to be done step by step 100/200/350/500. 100>350 might work directly - 100>500 does not work in one step.
100 > 350 > 500 seems to work, but 100 > 500 is accepted but does not produce a viable result.
But it should be possible to downgrade BW via MCBD command.
Yes, this works.
-
Hello,
now that i am at home i tried it again:
It works, not sure what was wrong bevor.
Two things: i can change 100MHz to 500MHz in one step
and the second thing is
it works only via Network/Webbrowser, not via entering the codes via touchscreen.
iwnug
-
Two things: i can change 100MHz to 500MHz in one step
Yes you can, but your scope will not work properly at higher frequencies.
Would probably have been best to follow the advice of many that have been down that path and back before. Now you'll have to go back to 100MHz and do it properly to get a full 500MHz +++.
I think you can skip the 200MHz, but you definitely cannot skip the 350MHz and still have things work out.
-
Hmm my probes are only rated for 100 and 200MHz, and I seem to remember 500MHz probes and actives probes costing a fortune. I forgot about that part.
This solution works really well and does not cost a fortune:
https://www.youtube.com/watch?v=llBzVa_SW_Q&t=35s (https://www.youtube.com/watch?v=llBzVa_SW_Q&t=35s)
-
Same process, same script. :popcorn:
Could SDS6204 uses the same script?
-
Hi,
No.
-
I'm running the latest software (5.0.1.5.2R3) and would like to get telnet access to try changing some of the logo files in the scope.
From what I have read I will need to access the hardware UART inside the scope to get terminal access, then enable telnetd. Is there any other way besides opening the scope? For those of you who have done it, do you just run an external cable to maintain access if needed?
Thanks for a great thread.
-
I'm running the latest software (5.0.1.5.2R3) and would like to get telnet access to try changing some of the logo files in the scope.
From what I have read I will need to access the hardware UART inside the scope to get terminal access, then enable telnetd. Is there any other way besides opening the scope? For those of you who have done it, do you just run an external cable to maintain access if needed?
Thanks for a great thread.
Please don't open the scope and please just continue reading.
-
I tried creating the siglent_device_startup.sh script on a FAT formatted USB drive with the following:
#!/bin/bash
/usr/sbin/telnetd -l /bin/sh -p 2323 &
Inserted drive, rebooted a few times but nothing happens, no telnet on port 2323.
Some other magic potion I should be looking for?
-
I tried creating the siglent_device_startup.sh script on a FAT formatted USB drive with the following:
#!/bin/bash
/usr/sbin/telnetd -l /bin/sh -p 2323 &
Inserted drive, rebooted a few times but nothing happens, no telnet on port 2323.
Some other magic potion I should be looking for?
That feature has been disabled. There are no public ways of getting a shell with the newest firmware.
-
Please don't open the scope and please just continue reading.
Thanks, I read a bit more and changed the little logo in the top right.
-
And what is that good for?
-
And what is that good for?
It makes him happy. 🤷
-
He wrote recessim.
Latin for "backward" with the meaning of reverse engineering.
Still better than logir ;-)
-
The new firmware has a new sw option (ARINC). Can someone tell me which keyword of this function is used in the script?
-
Add the 'A429' option name to the Python code and generate a key for the option. I just did this.
It works fine!
-
Hi all, just got a 2104 plus , I think the replit link that most people refer to for instructions to connect to scope, keygen, script, is down or expired.
apologies in advance if i missed it, if someone can give me the word to search in this or any post to get the most valid and up to date information to hack the scope i'd appreciate it.
also, it seems to be in contention whether bandwidth upgrade should go in increments, or all in one go. I'm going to err on the side of incrementing, also the explanation seemed the more plausible. has the question of one time bw vs increment upgrade bw settled?
-
Hi all, just got a 2104 plus , I think the replit link that most people refer to for instructions to connect to scope, keygen, script, is down or expired.
apologies in advance if i missed it, if someone can give me the word to search in this or any post to get the most valid and up to date information to hack the scope i'd appreciate it.
also, it seems to be in contention whether bandwidth upgrade should go in increments, or all in one go. I'm going to err on the side of incrementing, also the explanation seemed the more plausible. has the question of one time bw vs increment upgrade bw settled?
Welcome to the forum.
FYI, a 500 MHz BW upgrade is only possible from a preexisting 350 MHz model/license.
-
thanks tautech, I should have joined a long time ago.
I'm going to have a go with the cheap active probe method in the youtube above, I'll share my findings. Found the 1103 PSU on ebay from a liquidator not far from me. Still waiting for a more complete probe (with tip and gnd clip) to show up.
-
Hi,
what about script compatibility with SDS2000X HD?
or maybe other solution for HD series?