I have the SPD3303X-E and so I want to practice on it for when I get an AWG and scope. I'm on Windows 10, and I know very little about programing, LAN, firmware, hacking, LINUX, UNIX....although I'm enough of a tech geek to watch talks on some of this for fun.
What do I know so far, I got the Easypower and N.I. software installed and had Easypower running the PSU over USB and it works nicely.
So I un-hooked the USB and hooked up a LAN cable, and my PC and the PSU are blinking the LAN icon. The DCHP button is on, but the IP, NetMask, GateWay are all zero's. Is that supposed to be allowed ?
I ran IPCONFIG and found a device on the ethernet, so that must be it on my mobo. So I went into the PSU LAN settings and set it to what IP config said., it said nothing for gateway, so does that mean set 0's ? That's what I did.
Nothing in Win10 has said 'new LAN decive connected", where-as over USB it did some auto-setup.
So IDK if I need software for LAN ? I DL'ed some telnet program called Putty, and something else called busybox for a later step.
But for all I know all this is meant for LINUX.
For now I just what to try part of this
What do I know so far, I got the Easypower and N.I. software installed and had Easypower running the PSU over USB and it works nicely.
So I un-hooked the USB and hooked up a LAN cable, and my PC and the PSU are blinking the LAN icon. The DCHP button is on, but the IP, NetMask, GateWay are all zero's. Is that supposed to be allowed ?
I ran IPCONFIG and found a device on the ethernet, so that must be it on my mobo. So I went into the PSU LAN settings and set it to what IP config said., it said nothing for gateway, so does that mean set 0's ? That's what I did.
Nothing in Win10 has said 'new LAN decive connected", where-as over USB it did some auto-setup.
So IDK if I need software for LAN ? I DL'ed some telnet program called Putty, and something else called busybox for a later step.
But for all I know all this is meant for LINUX.
For now I just what to try part of this
vt100
![]()
Re: Siglent .ads firmware file format
« Reply #212 on: October 08, 2018, 03:13:09 am »
This process will obtain your license keys from a core dump of the scope application itself, in case you lost the paperwork after you purchased them (of course). No "guessing games" like the other software posted (although it was a fun intellectual exercise!)
Skill level: Easy/Moderate
Risk: Slim to none.
Assumptions: You know the root password to your scope.
Steps:
1. download full armv7l version of busybox which has core dump enabled.
see: https://busybox.net/downloads/binaries/1.28.1-defconfig-multiarch/busybox-armv7l
2. put version on thumb disk
3. reboot scope to known state
4. telnet to scope and log in as root
5. insert usb stick
6. copy busybox binary from usb to /tmp:
cp /usr/bin/siglent/usr/mass_storage0/U-disk/busybox-armv7l /tmp
7. unmount and remove usb
umount /usr/bin/siglent/usr/mass_storage/U-disk0
(and then remove usb stick)
8. identify and kill existing sds1000b.app
ps -ef | grep sds | awk '{printf "kill -9 %s\n", $1}' | ash
9. change to /tmp directory:
cd /tmp
10. launch new busybox ash shell
/tmp/busybox_armv7l ash
(when you press enter it looks like nothing happens, but something does)
11. re-launch scope app in new busybox environment in background
/usr/bin/siglent/sds1000b.app &
12. increase core dump ulimit to unlimited:
ulimit -c unlimited
you can verify new limit by typing
ulimit -c
and you should get a response "unlimited"
12. kill scope app again, telling OS to create a core dump of the app:
ps -ef | grep sds | awk '{printf "kill -ABRT %s\n", $1}' | ash
13. wait a few seconds, and press enter once or twice. you should see:
[1]+ Aborted (core dumped) /usr/bin/siglent/sds1000b.app
if you do not, you did something wrong, go to step #3
14. verify core dump is in /tmp:
ls /tmp/core*
you should see something like this:
-rw------- 1 root root 377511936 Jan 1 00:14 /tmp/core
if not, you did something wrong, go to step #3
15. exit out of usb version of busybox shell
exit
(it will look like nothing happens when you press enter, but, something does)
16. re-launch Siglent scope application. See Step #11
17. insert usb drive
18. copy core dump to thumb drive
cp core /usr/bin/siglent/usr/mass_storage/U-disk0/coredump.bin
(this will take a minute or two, its a big file)
19. unmount usb stick and remove (see step #7)
20. Insert USB stick on Windows/Mac/Linux and open the coredump.bin file in your favorite hex editor.
21. Search for string "SDS1000X-E". Keep searching until you find the string next to either your scopeid (if you do not know your scope id, you can get it using the SCPI SCOPEID? command thru the web interface) or your serial number.
22. When you locate the entry with your scope ID, you will see a series of 5 16-character strings below it (one will look like a 32 character string, split it into half so you have two 16-character strings. These are your 100, 200, 50 and 70 mhz license keys, respectively. The one that appears twice is the license key your scope is currently licensed under.
23. You can license a different bandwidth by typing MCBD (license key) at the scope's SCPI web interface. It is necessary to reboot after you do this for everything to reset and take effect. You can verify the bandwidth by typing PRBD? through the SCPI web interface.
24. When you locate the entry with your serial number, you will see a series of (at least) 3 16-character strings. If you have any options already licensed, those keys will appear twice. if you have no options licensed, they only appear once. The keys are, respectively, AWG, WIFI and MSO.
25. You can license any options through the scope's SCPI interface using LCISL (option),(key) where (option) is AWG, WIFI or MSO and (key) is the 16-character key.
26. after doing so, even though the options are immediately licensed and active, I recommend a reboot for the new options to take effect.
27. Write keys down in a safe place so you do not lose them again.
Last edited: